테스트·보안 스킬

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bun runtime, package manager, bundler, and test runner. Use when running scripts with bun, managing packages, serving HTTP with Bun.serve, querying databases with Bun.sql/bun:sqlite/Bun.redis, shell scripting with $, using S3/file I/O, writing tests with bun:test, bundling or compiling to executable, or using any Bun-specific API (spawn, glob, semver, FFI, workers, plugins, HTMLRewriter).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test, fold or refute hypotheses beside the knowledge record, and reconcile records across branches. Use when open or check say hypotheses wait or an id is CONTESTED, when a write was refused into a hypothesis, before merging a branch whose record changed, and when a pull request's dry run or remeasure is red. Covers consolidate --dry-run, the fold, --refute, --from, same and distinct at the fold, and remeasure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Workflow] Build or extend idempotent, environment-gated development/QC seeders with realistic data, change review and verified tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Workflow] Audit project architecture, scalability and production readiness without changing code; deliver one consolidated health report.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Documentation] Use when generating the DERIVED technical spec view over code and tests, or reporting §8 TC drift. Generator only, never authors business content. generate|audit|sync.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Documentation] Use when a workflow step or the user asks for canonical feature specs and test scenarios: author, audit, amend, tests and sync. discovery maps overlaps; clarify confirms decisions; index derives navigation/ERD.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Workflow] Use when E2E tests need to be written, updated or fixed: resolves the scope, authors tests only when needed, then verifies them through the configured runner in a bounded fix/retest loop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Dev Data] Use when a workflow step or the user asks for idempotent QC happy-path seeders using public commands. --mode=review audits seeder conventions read-only.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Testing] Use when a workflow step or the user asks for a local test run and read-only results summary.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Process] Use when a developer needs to understand and judge scoped work: a change set, subsystem, decision, plan or concept — flow, rationale, trade-offs, testing. Bugs: investigate --mode=debug; one feature's code flow: investigate.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Implementation] Use when a workflow step or the user asks for root-cause fixes with regression coverage. --target={ci|issue|logs|review|test|types|ui} scopes the issue.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Testing] Use when a workflow step or the user asks for integration test generation, diagnosis or traceability checks. --mode=review checks test quality; --mode=verify runs tests, with optional --fix-loop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Testing] Use when a workflow step or the user asks for E2E test selection, generation or updates. --mode=verify runs tests; --fix-loop repairs failures; --visual-review={true|false}.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Implementation] Use when the user asks to build a feature from an idea or description with no plan file yet: research and trace the code, create and get the plan approved, build each phase with its tests, review, verify once, sync specs and docs. Existing plan: plan --mode=execute.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for Devin/GitHub/security bot comments, verifying whether requested corrections were applied, and turning pending fixes into SPECs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to implement an approved SPEC SDD using test-driven development.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchestrated execution via orchestrator, with an explicit approval gate before any external action.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when raising code quality or test coverage across a .NET, Java, or Python repository.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.