테스트 설계, 취약점 진단, 품질 보증 (1.3만건)
Use when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shared discipline for every hunt-* skill: scope and authorization gating, the two-account rule, the confirmation gate that separates a real finding from a false positive, enumeration limits, stop conditions, marker discipline, wiki-first query and self-heal, FIND output, Deadends, and wiki distillation. ALWAYS LOADED alongside any hunt skill. Also trigger directly on "is this in scope", "is this a real bug", "how do I confirm this", "should I keep going", "how many IDs should I test", "what severity", "how do I report this", "I got someone else's data". Every hunt-* skill assumes this file; without it they run without their safety and quality layer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
OFFLINE FALLBACK for the claude-md-management plugin - prefer that plugin when it is installed. Audit and improve CLAUDE.md files - scan for CLAUDE.md files, evaluate quality against templates, output a report, then make targeted updates. Invoke explicitly (/claude-md-improver) when the plugin is unavailable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
IDOR / BOLA hunting - two-account methodology, identifier discovery and UUID leak chaining, the trusted-identifier test, GraphQL node and nested-object IDOR, cross-tenant escalation, write and delete operations. Bounded ID sampling, never range sweeps. Wiki-first, FIND schema output. Trigger on IDOR, BOLA, broken access control, object level authorization, cross-tenant, "read another user's data", "swap the id", or any API path or parameter carrying a numeric ID, UUID, or account identifier.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates an existing package Skill for a new release of its npm or local package by testing only what changed since the version the Skill names. Use when a maintainer asks to refresh a package Skill after a release, or when a SKILL.md names an older tested version than the package.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate or update an Agent Skill that teaches consumers one npm or local package the user maintains, including framework modules and wrappers. Tests each example against the installed version. Use when a maintainer asks for a package Skill, a SKILL.md for their library, or a Skill update after a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or fix PromQL queries and alerting rules; detects anti-patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or check Jenkinsfiles and shared libraries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, check Helm charts — Chart.yaml, templates, values.yaml, CRDs, schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or fix .gitlab-ci.yml pipelines, stages, and jobs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or check Fluent Bit configs (INPUT, FILTER, OUTPUT, tag routing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or fix bash/shell/.sh scripts via ShellCheck.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or check Terragrunt .hcl/terragrunt.hcl files, stacks, modules, compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or check Makefiles and .mk files for errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate, lint, audit, or debug Ansible playbooks, roles, inventories, FQCN, tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing tests of any kind — unit, slice, or integration. Covers test structure, naming conventions, Mockito patterns, @WebMvcTest, @DataJpaTest, and Testcontainers setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when preparing a Spring Boot 3 application for Boot 4, upgrading to Boot 3.5 first, removing deprecated APIs, auditing dependencies, or planning a staged Framework 7 migration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an application issues and validates its own first-party JWT access and refresh tokens, including authentication filters, password encoding, RBAC, and method security. For JWTs issued by Keycloak, Auth0, Okta, Cognito, or another authorization server, use oauth2-resource-server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Before showing the user any substantive GTM deliverable (positioning, value prop, homepage, launch post, pricing, sales script, the brief, the market research, or the roadmap), stress-test it against the standard as an independent critic, because the agent that wrote it is the worst judge of whether it is good. Use as a gate right before presenting work, or when the user asks whether something is actually strong.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structure a dev-tool homepage that converts developers into champions. Use when the landing page is written for the buyer instead of the developer, reads as salesy, buries what the product does, or makes it hard to start. Pairs with the ShipReady homepage audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evidence-based investigation of issues, bugs, API calls, integrations, and other aspects of software development that need a deep dive to find the root cause and solutions. Use when you need to debug, troubleshoot, diagnose, or figure out why something is broken. Does not review code for quality or style — use code-review for auditing changes or post-code-review-to-pr for posting review feedback to GitHub. Does not assess architectural health or structural risk — use architectural-analysis for architectural concerns. Does not research open-ended options, prior art, or how something works when nothing is broken — use research for that. Does not plan the structural change a root cause calls for — use plan-a-change. Does not map bounded contexts or domain boundaries — use ddd-analysis. Does not capture feedback on Han's own skills — use han-feedback for that.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation. Produces a feature specification focused on system behaviors, not implementation detail. Does not plan a restructure of code that already exists — use plan-a-change. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features — use project-documentation. Does not design the contract for an interface — use design-an-api. Does not research open-ended options before there is a feature to specify — use research. Does not map the bounded contexts of existing code — use ddd-analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan. Also use it when the user asks to verify, validate, or confirm feasibility of an approach. Does not implement plan steps, write test plans, review code, or investigate bugs, and does not generate new plans from scratch — use plan-a-feature for a new plan. Runs its review rounds to completion without pausing between them; to review each round as it lands, use pairing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build work collaboratively in reviewable pieces, handing each piece back for review before starting the next, so the person stays in the lead and steers while the work happens instead of reviewing a finished result. Use when someone says to pair with them on something, asks to collaborate rather than direct, wants to review as it goes, or wants to guide the work piece by piece — on code, on a design decision, or on writing. For a test-first build it runs tdd, for restructuring it runs refactor, for an interface contract it runs design-an-api, and for plan work it runs iterative-plan-review or plan-implementation, each collaboratively; invoke any of those directly instead to run it straight through without pausing. Does not pace someone through code that already exists and builds nothing — use code-walkthrough. Does not explain, summarize, or research something instead of producing it — use code-overview or research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.