메뉴
Author or refine an inspequte rule spec from a rule idea, optional plan.md, and target rule-id. Use when writing src/rules/<rule-id>/spec.md from a fixed template while avoiding implementation details.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Fix Rust dependency audit failures in inspequte by reading cargo audit SARIF output, updating Cargo.toml or Cargo.lock with minimal dependency changes, and verifying with cargo build, cargo test, and cargo audit.
Launch Jaeger, run SpotBugs benchmark traces, capture Jaeger UI screenshots via the shared `scripts/capture-jaeger-trace-screenshot.mjs` helper, and report bottlenecks by rule, jar, and class for inspequte. Use when asked to profile `scripts/bench-spotbugs.sh`, inspect Jaeger traces, save screenshots under `target/bench`, and explain the slowest components.
Run inspequte false-positive hunting against small OSS libraries (Kotlin and Java+Guava), enable inspequte-gradle-plugin in cloned fixtures, capture Jaeger trace screenshots via the shared `scripts/capture-jaeger-trace-screenshot.mjs` helper, and triage SARIF findings one by one.
Capture a Jaeger trace screenshot for a specified trace ID via `scripts/capture-jaeger-trace-screenshot.mjs`. Use when a trace ID is already known and the task is only to capture and return a deterministic screenshot artifact path.
Resume a rule implementation that was marked No-Go in GitHub Actions by importing plan/spec/impl from a PR, completing missing behavior and tests, and marking the rule as implemented in no-go-history.
Implement an inspequte rule from spec.md, including tests and minimal docs updates. Use when coding src/rules/<rule-id>/mod.rs and related tests while treating spec.md as immutable unless explicitly asked to change it.
| name | inspequte-rule-spec |
| description | Author or refine an inspequte rule spec from a rule idea, optional plan.md, and target rule-id. Use when writing src/rules/<rule-id>/spec.md from a fixed template while avoiding implementation details. |
rule-id.src/rules/<rule-id>/plan.md.src/rules/<rule-id>/spec.md.Use this exact section order:
## Summary## Motivation## What it detects## What it does NOT detect## Examples (TP/TN/Edge)## Output## Performance considerations## Acceptance criteriasrc/rules/AGENTS.md.src/rules/<rule-id>/spec.md if present.src/rules/<rule-id>/plan.md if present.spec.md as a behavior contract, not a design doc.## Summary, define intended rule metadata (id, name, description) clearly so implementation can map it directly.@Suppress-style suppression is unsupported, and only JSpecify annotations are supported for annotation-driven semantics.spec.md exists under the target rule directory.