How do I install the Tools Bug Scan skill?

Run npx skillmds@latest add majiayu000/tools-bug-scan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tools Bug Scan safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tools Bug Scan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tools Bug Scan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tools Bug Scan?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tools Bug Scan by majiayu000 — Agent Skill

Name: Tools Bug Scan
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Bug Scan Tool

Use this skill when the user wants a fast, deterministic bug-pattern sweep using the in-repo scanner.

Commands

Full/targeted scan:
- pnpm bug-scan [path ...]
Changed-files scan:
- pnpm bug-scan:changed
Machine-readable output:
- pnpm bug-scan -- --format=json [path ...]
- pnpm bug-scan -- --changed --format=json
- pnpm bug-scan -- --changed --format=json --fail-on=none --business-scope=<BIZ> --idea-artifact=docs/plans/<slug>/bug-scan-findings.user.json
Rule discovery and tuning:
- pnpm bug-scan:rules
- pnpm bug-scan -- --changed --fail-on=critical
- pnpm bug-scan -- --only-rules=<ruleA,ruleB>
- pnpm bug-scan -- --skip-rules=<ruleA,ruleB>
- pnpm bug-scan -- --write-baseline=tools/bug-scan-baseline.json --fail-on=none
- pnpm bug-scan -- --baseline=tools/bug-scan-baseline.json

Default Workflow

Choose scope:
- If user asks for changed work, run pnpm bug-scan:changed.
- If user provides files/directories, pass them to pnpm bug-scan.
- If unspecified, prefer changed-files first to keep signal high.
Run scanner once.
If findings exist, summarize by:
- severity counts (critical, warning)
- rule IDs
- top file locations (path:line:column)
Recommend a concrete next action set:
- immediate fixes for critical
- optional cleanup queue for warning
- exact rerun command after fixes
If the scan is part of post-build reflection, write the idea artifact into the active plan directory so startup-loop:generate-process-improvements can ingest findings as idea candidates.

Output Contract

Always report:

Scan scope used.
Finding totals by severity.
Top findings with file references.
Exit status implication:
- 0 = no findings
- 1 = findings present

Guardrails

Do not install external scanners or mutate hooks/shell profiles in this skill.
Do not fail the task if scanner reports findings; report and propose fix order.
If scanner command fails for runtime/tooling reasons, report the error and suggest the minimal unblocking command.

Escalation

Escalate to planning (lp-do-fact-find / lp-do-build) when:

the same rule repeatedly appears across many files,
findings indicate systemic pattern debt,
user asks to convert findings into an implementation plan.

---name: tools-bug-scandescription: Run the repository-native bug scanner (`pnpm bug-scan` / `pnpm bug-scan:changed`), summarize findings by severity and rule, and propose concrete next fixes or targeted rescans.--- # Bug Scan Tool Use this skill when the user wants a fast, deterministic bug-pattern sweep using the in-repo scanner. ## Commands - Full/targeted scan: - `pnpm bug-scan [path ...]` - Changed-files scan: - `pnpm bug-scan:changed` - Machine-readable output: - `pnpm bug-scan -- --format=json [path ...]` - `pnpm bug-scan -- --changed --format=json` - `pnpm bug-scan -- --changed --format=json --fail-on=none --business-scope=<BIZ> --idea-artifact=docs/plans/<slug>/bug-scan-findings.user.json` - Rule discovery and tuning: - `pnpm bug-scan:rules` - `pnpm bug-scan -- --changed --fail-on=critical` - `pnpm bug-scan -- --only-rules=<ruleA,ruleB>` - `pnpm bug-scan -- --skip-rules=<ruleA,ruleB>` - `pnpm bug-scan -- --write-baseline=tools/bug-scan-baseline.json --fail-on=none` - `pnpm bug-scan -- --baseline=tools/bug-scan-baseline.json` ## Default Workflow 1. Choose scope: - If user asks for changed work, run `pnpm bug-scan:changed`. - If user provides files/directories, pass them to `pnpm bug-scan`. - If unspecified, prefer changed-files first to keep signal high. 2. Run scanner once. 3. If findings exist, summarize by: - severity counts (`critical`, `warning`) - rule IDs - top file locations (`path:line:column`) 4. Recommend a concrete next action set: - immediate fixes for `critical` - optional cleanup queue for `warning` - exact rerun command after fixes 5. If the scan is part of post-build reflection, write the idea artifact into the active plan directory so `startup-loop:generate-process-improvements` can ingest findings as idea candidates. ## Output Contract Always report: - Scan scope used. - Finding totals by severity. - Top findings with file references. - Exit status implication: - `0` = no findings - `1` = findings present ## Guardrails - Do not install external scanners or mutate hooks/shell profiles in this skill. - Do not fail the task if scanner reports findings; report and propose fix order. - If scanner command fails for runtime/tooling reasons, report the error and suggest the minimal unblocking command. ## Escalation Escalate to planning (`lp-do-fact-find` / `lp-do-build`) when: - the same rule repeatedly appears across many files, - findings indicate systemic pattern debt, - user asks to convert findings into an implementation plan.

Frequently asked questions

Tools Bug Scan