Automatically finds and fixes bugs in the codebase.

Install

mkdir -p .claude/skills/gsd-audit-fix && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12643" && unzip -o skill.zip -d .claude/skills/gsd-audit-fix && rm skill.zip

Installs to .claude/skills/gsd-audit-fix

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
75 charsno explicit “when” trigger
Advanced

Key capabilities

  • Run an autonomous audit.
  • Classify findings as auto-fixable or manual-only.
  • Autonomously fix auto-fixable issues.
  • Verify fixes with tests.
  • Commit changes atomically.

How it works

The skill executes an audit-to-fix workflow that finds issues, classifies them, autonomously fixes auto-fixable ones, verifies with tests, and commits changes.

Inputs & outputs

You give it
Optional flags for max findings, severity, dry-run, or audit source.
You get back
Fixed issues, test verification results, and atomic commits.

When to use gsd-audit-fix

  • Auto-fixing bugs
  • Auditing code quality
  • Autonomous issue resolution

About this skill

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-audit-fix.
  • Treat all user text after $gsd-audit-fix as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected or unavailable, activate TEXT_MODE: append --text to {{GSD_ARGS}} so the workflow's built-in text-mode branching takes over. Present every AskUserQuestion call as a plain-text numbered list, then stop and wait for the user's reply. Do NOT pick a default and continue (#3018 / #3808).
  • You may only proceed without a user answer when one of these is true: (a) the invocation included an explicit non-interactive flag (--auto or --all), (b) the user has explicitly approved a specific default for this question, or (c) the workflow's documented contract says defaults are safe (e.g. autonomous lifecycle paths).
  • Do NOT write workflow artifacts (CONTEXT.md, DISCUSSION-LOG.md, PLAN.md, checkpoint files) until the user has answered the plain-text questions or one of (a)-(c) above applies. Surfacing the questions and waiting is the correct response — silently defaulting and writing artifacts is the #3018 failure mode.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Agent(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit. spawn_agent has no inline model parameter; GSD embeds the resolved per-agent model directly into each agent's .toml at install time so model_overrides from .planning/config.json and ~/.gsd/defaults.json are honored automatically by Codex's agent router.
  • Resolved reasoning_effort="low|medium|high|xhigh" (xhigh is a GSD/Codex tier, not a generic runtime enum) → pass reasoning_effort to spawn_agent when the runtime/tool supports it. Omit missing, empty, inherited, or unsupported values; do not invent one-off effort literals in workflow prose.
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks
  • Task(isolation="worktree") / Agent(isolation="worktree") → no direct Codex mapping. Codex spawn_agent does not create or bind a git worktree automatically. Workflows that require this isolation must fail closed or use an explicit manual worktree protocol before spawning (#3360).

Spawn restriction:

  • Codex restricts spawn_agent to cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.
  • In some Codex sessions, multi-agent tooling can be deferred. If spawn_agent is not currently visible, discover tools first via tool_search before defaulting to inline execution.

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<objective> Run an audit, classify findings as auto-fixable vs manual-only, then autonomously fix auto-fixable issues with test verification and atomic commits.

Flags:

  • --max N — maximum findings to fix (default: 5)
  • --severity high|medium|all — minimum severity to process (default: medium)
  • --dry-run — classify findings without fixing (shows classification table)
  • --source <audit> — which audit to run (default: audit-uat) </objective>

<execution_context> @/Users/mali/Development/xai-bookkeeping/.codex/get-shit-done/workflows/audit-fix.md </execution_context>

<process> Execute end-to-end. </process>

When not to use it

  • When the task is not related to an audit-to-fix pipeline.

Limitations

  • Codex has no `multiSelect` for user input.
  • Codex `spawn_agent` does not create or bind a git worktree automatically.
  • Codex restricts `spawn_agent` to cases where the user has explicitly requested sub-agents.

How it compares

This skill automates the entire audit-to-fix cycle, including classification, fixing, testing, and committing, unlike a manual process of identifying and resolving issues.

Compared to similar skills

gsd-audit-fix side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-audit-fix (this skill)02moNo flagsAdvanced
bats97moReviewIntermediate
browser-daemon59moReviewIntermediate
examples-auto-run23moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

bats

OleksandrKucherenko

Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.

991

browser-daemon

noiv

Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.

587

examples-auto-run

openai

Run python examples in auto mode with logging, rerun helpers, and background control.

23

workflow-test-fix-cycle

catlog22

End-to-end test-fix workflow generate test sessions with progressive layers (L0-L3), then execute iterative fix cycles until pass rate >= 95%. Combines test-fix-gen and test-cycle-execute into a unified pipeline. Triggers on "workflow:test-fix-cycle".

12

qoobee-t&f-skill

Piaoxuemoli

Test & Fix skill for ImmerseAI. Supports automated testing (Agent runs code audits and auto-fixes) and manual test report fixing (Agent parses human test reports and fixes failures). Trigger with: 自动化测试, 自动测试, auto test, 人工测试, manual test, 测试报告, test report, 运行测试, run tests.

00

validate-run

SprocketLab

Validate all checkpoints from an agent run directory in parallel. Spawns test-validator agents for each checkpoint and summarizes results. Invoke with /validate-run <run_path> [problem].

00

Search skills

Search the agent skills registry