audit-and-fix
From the author
Audit an existing codebase, then autonomously implement the fixes it judges worth making against your next goal — composing deep-dive → triage → prompt-pack → build-loop to turn "here's what's wrong" into verified, receipted local commits + an honest ledger. ALWAYS invoke when the user says any of "audit this repo and fix what you find", "audit and edit", "deep dive then fix the bugs", "implement the audit's recommendations", "plan and execute these fixes", or "autopilot this repo but skip the ideation". It composes those skills, never reimplementing them. Honest bounds: a receipt records what ran, it never proves correctness; the deep-dive→triage→pack half is proven, the build-loop seam is not; local commits only, never push/merge/tag/publish. Do NOT use to audit with no intent to change (deep-dive), for a change you already know you want (prompt-pack + build-loop), for a new idea with no codebase (autopilot), or for feature work — it fixes what the audit found, nothing more.
Install
npx skills add nelsonwerd/idea-to-ship-skills --skill audit-and-fix -a claude-code
Installs to .claude/skills/audit-and-fix/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 81
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- audit-projectOutlineDriven/outline-driven-developmentUse when the user says "audit my code", "find all the bugs", "review until clean", or "grill my changes". Not for remote, credential, or irreversible changes.Engineering★ 54
- build-loopnelsonwerd/idea-to-ship-skillsDrive a build to actually-works, near-finish-line craft by looping build → see → exercise → check → critique → rebuild over the agent's existing tools (bash build/test, headless screenshot + vision, Playwright, axe/Lighthouse) until acceptance criteria pass or an explicit stop-condition fires — no infinite thrash. ALWAYS invoke when the user says any of "tighten this build", "iterate until it passes", "self-verify the UI", "make it actually work, not just compile", "loop until the core flows pass", or "drive this to near-finish-line". Also invoke proactively after a scaffold or feature lands and before handing a draft to a human. Composition-first over existing tools, not a new program; it states its own honest bounds — objective craft only, taste self-graded, ~80% ceiling, market validation out of scope. Do NOT use to decide WHAT to build (that's ideate) or whether a design/strategy is sound (deep-dive).Testing★ 90
- ai-debugarcasilesgroup/ai-engineeringFinds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves merge and rebase conflicts by intent rather than by taking a side. Trigger for "it's not working", "this used to work", "I'm getting an error", "CI is failing", "why is X happening", "I have conflicts", "the rebase failed". Not for adding test coverage to working code — use /ai-verify. Not for exploring an unfamiliar area — use /ai-explore. Not for designing the fix — once the cause is named, use /ai-orchestrator. Not for reporting the fault to outsiders — use /ai-issue-report.Engineering★ 61
- reviewjoetawil7/first-passReviews a change before it is merged, from little or no input. With nothing typed it reviews the branch you are on, uncommitted work included, against its base, its PR and its ticket, so a developer can check their own work before asking for review. With PR links, repo#N or a branch it reviews someone else's change the same way, several repos at once. It judges the failed CI checks and every Bugbot and reviewer comment, gets a fresh breaker review, traces every other piece of code that uses what changed, proves each finding or marks it unproven, says what the merge needs (a build, env vars, migrations, deploy order) and how to check the deploy, never posts to GitHub, and offers fixes only after the report. Runs only when the user types it.Engineering★ 113
- improvegadicc/yahoo-finance2Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.Security★ 808
- deepoprogramadorreal/optimus-claudeRuns an iterative auto-fix loop on a chosen target — review, refactor, or coverage — dispatching the base skill into fresh subagent contexts per iteration, applying fixes automatically without per-change approval, running tests with bisection on failure, and checkpoint-committing until convergence or the cap. Requires /optimus:init and a test command in .claude/CLAUDE.md.Testing★ 74
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in