How do I install the Pit Stop skill?

Run npx skillmds@latest add finn763/pit-stop 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 Pit Stop safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pit Stop?

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 Pit Stop free to use?

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

Who published Pit Stop?

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

Pit Stop by finn763 — Agent Skill

Name: Pit Stop
Author: Finn763

Pit Stop

Use when the user asks to fully improve, overhaul, audit-and-fix, clean up tech debt, or run pit-stop on a project, repo, or codebase. Triggers: 'improve this project', 'overhaul the repo', 'audit and fix everything', 'tech debt cleanup', 'pit-stop', '全面改进', '项目体检', '进站', '重构整个项目'.

Finn763 47eae6f 9 files · 13.1 KB Updated Sep 17, 2026

File contents

Pit-Stop

F1 pit-stop for codebases: drive in, get fixed, come out faster. One instruction runs load → find → propose → fix → ideas → report with no mid-run questions. The user only says go; you return once with a report.

The run (in order, no skipping)

Load: read README/AGENTS.md (or equivalent) + git status + recent-commit hot spots. Write one line first: MODE = what counts as a finding here, what is rejected outright. Missing a key fact? Ask ONCE, then proceed under strictest defaults.
Find: scope before you scan (named target > git hot spots > full tree). Every finding needs path:line evidence. Skip recorded decisions unless friction justifies reopening. Tag each: delete/stdlib/native/yagni/shrink/perf/security/obs, strength Strong/Worth/Speculative. Speculative = report only, never fix. Nothing found: say Lean already. Ship. — never pad.
Propose: Strong items only. Each = symptom + evidence + impact + minimal fix + cost. Plus a NOT-doing list with its trigger conditions.
Fix: review→fix loop with an independent reviewer (different angle beats same eyes); stop at clean or --max-rounds (default 3). Cross-round ledger, no repeat fixes. Two stagnant rounds → escalate to "needs human", stop. See references/review.md.
Ideas: after the loop closes, read-only brainstorm — no edits, no subagent. ≤3 candidates, each anchored in this run's ledger/diff, shaped [idea] <capability ≤20 words> — <path:line> — probe: <≤12 words>. Never built this run. See references/ideas.md.
Report: header Generated fully automatically by pit-stop. Four blocks — changed / verified (tool output) / unverified / remaining. No claim without fresh tool output. Secret/token/PII redaction in everything pasted. The ideas ride behind needs-human items in Remaining. See templates/report.md.

Iron laws

Evidence before claims, always. No verification run in this turn = no success claim.
A subagent's "done" is not done. Read its diff before reporting.
Fuzzy spots downgrade, never guess. Write "needs human", keep moving.
Push/commit never automatic. Changes wait in the workdir for one explicit word.
Single spend fuse: one phase estimated over $20 → stop phase, write report.

Details: references/audit.md, references/fix.md, references/review.md, references/report.md, references/ideas.md, references/guardrails.md, references/verification.md.

---name: pit-stopdescription: Use when the user asks to fully improve, overhaul, audit-and-fix, clean up tech debt, or run pit-stop on a project, repo, or codebase. Triggers: 'improve this project', 'overhaul the repo', 'audit and fix everything', 'tech debt cleanup', 'pit-stop', '全面改进', '项目体检', '进站', '重构整个项目'.---# Pit-StopF1 pit-stop for codebases: drive in, get fixed, come out faster. One instruction runs**load → find → propose → fix → ideas → report** with no mid-run questions. The user only says go;you return once with a report.## The run (in order, no skipping)1. **Load**: read README/AGENTS.md (or equivalent) + `git status` + recent-commit hot spots. Write one line first: MODE = what counts as a finding here, what is rejected outright. Missing a key fact? Ask ONCE, then proceed under strictest defaults.2. **Find**: scope before you scan (named target > git hot spots > full tree). Every finding needs `path:line` evidence. Skip recorded decisions unless friction justifies reopening. Tag each: `delete/stdlib/native/yagni/shrink/perf/security/obs`, strength `Strong/Worth/Speculative`. Speculative = report only, never fix. Nothing found: say `Lean already. Ship.` — never pad.3. **Propose**: Strong items only. Each = symptom + evidence + impact + minimal fix + cost. Plus a NOT-doing list with its trigger conditions.4. **Fix**: review→fix loop with an independent reviewer (different angle beats same eyes); stop at clean or `--max-rounds` (default 3). Cross-round ledger, no repeat fixes. Two stagnant rounds → escalate to "needs human", stop. See `references/review.md`.5. **Ideas**: after the loop closes, read-only brainstorm — no edits, no subagent. ≤3 candidates, each anchored in this run's ledger/diff, shaped `[idea] <capability ≤20 words> — <path:line> — probe: <≤12 words>`. Never built this run. See `references/ideas.md`.6. **Report**: header `Generated fully automatically by pit-stop`. Four blocks — changed / verified (tool output) / unverified / remaining. No claim without fresh tool output. Secret/token/PII redaction in everything pasted. The ideas ride behind needs-human items in Remaining. See `templates/report.md`.## Iron laws- **Evidence before claims, always.** No verification run in this turn = no success claim.- **A subagent's "done" is not done.** Read its diff before reporting.- **Fuzzy spots downgrade, never guess.** Write "needs human", keep moving.- **Push/commit never automatic.** Changes wait in the workdir for one explicit word.- **Single spend fuse**: one phase estimated over $20 → stop phase, write report.Details: `references/audit.md`, `references/fix.md`, `references/review.md`,`references/report.md`, `references/ideas.md`, `references/guardrails.md`,`references/verification.md`.

Frequently asked questions