code-audit
Code Audit
Parallel codebase quality review that orchestrates the code-simplifier and design-critic skills via subagents, then consolidates and presents findings.
Workflow
Phase 1: Parallel Analysis
Launch two general-purpose subagents in parallel using the Task tool:
Subagent A — Code Simplifier
Prompt the subagent to use the code-simplifier skill (via the Skill tool) against the current working directory. Instruct it to:
- Scan source files for complexity hotspots, unnecessary abstractions, and simplification opportunities
- Return a structured list of findings, each with: file path, line range, issue summary, suggested fix, and severity (high/medium/low)
Subagent B — Design Critic
Prompt the subagent to use the design-critic skill (via the Skill tool) against the current working directory. Instruct it to:
More from arjenschwarz/agentic-coding
ui-ux-reviewer
Evaluate and improve user experience of interfaces (CLI, web, mobile)
129efficiency-optimizer
Analyze code for performance and efficiency improvements
42design-critic
Critical review of design documents, architecture proposals, and requirements
26fix-bug
Systematic bug investigation, resolution, and documentation. Use when fixing bugs that need thorough analysis, test coverage, and a formal bugfix report. Applies systematic debugging methodology, creates regression tests, and generates a standardized report in specs/bugfixes/<bug-name>/. For complex bugs, spawns competing implementation agents (including alternative harnesses like Kiro) and selects the best solution. Triggers on requests like "fix this bug", "debug and document this issue", or when a bug needs both resolution and documentation.
22permission-analyzer
Generate Claude Code permissions config from session history. Use when setting up autonomous mode, configuring .claude/settings.json, avoiding --dangerously-skip-permissions, or analyzing what permissions a project needs. Reads session logs to extract Bash commands and MCP tools actually used, then generates appropriate allow/deny rules.
22performing-systematic-debugging-for-stubborn-problems
Applies a modified Fagan Inspection methodology to systematically resolve persistent bugs and complex issues. Use when multiple previous fix attempts have failed repeatedly, when dealing with intricate system interactions, or when a methodical root cause analysis is needed. Do not use for simple troubleshooting. Triggers after multiple failed debugging attempts on the same complex issue.
20