Menu
Code cleanliness — AI-generated slop, naming, dead code, over-engineering, simplification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
Cross-repo visibility for agent loops. Lists running, completed, and crashed loops. Reads the registry and per-repo tracking logs. Shows tmux attach commands. Use when checking what loops are active, what ran recently, or loop details.
Capture feedback about wf, util, or vault plugins and file it as a GitHub issue for improvement. Use after any session where the tooling fell short — wrong agent behavior, missing skill coverage, misleading prompts, workflow friction, or convention gaps. Only for generic plugin improvements that would help ANY project, not repo-specific config. Files to JSai23/claude-tooling with the plugin-feedback label.
Write high-quality session prompts (SESSION_WORKER.md and SESSION_REVIEWER.md) for an agent loop. Reads repo context and follows the loop-author guide to produce targeted, effective prompts. Use when setting up a new loop or rewriting session prompts for an existing one.
Pre-flight checks and launch for agent loops. Validates branch state, session prompts, creates loop directory structure, and launches run.sh in a tmux session. Use when the user wants to start a new agent loop in the current repo.
| name | verify-style-a |
| type | action |
| description | Code cleanliness — AI-generated slop, naming, dead code, over-engineering, simplification |
| user-invocable | false |
Action skill — Code cleanliness review: AI slop detection, naming, dead code, fix protocol, output format.
Line-level code quality without changing behavior.
Defensive code — Try/catch around code that can't fail. Null checks on values that are never null. Fallbacks for impossible cases. Validation of internal values guaranteed by the type system.
Over-engineering — Abstractions for one-time operations. Interfaces with single implementations. Factory patterns for simple construction. Configuration for things that will never be configured.
Verbosity — Multiple lines that could be one. Intermediate variables that add nothing. Obvious comments that restate the code.
Naming — Unclear names. Inconsistent naming across similar modules. Abbreviations that aren't obvious. Names that lie.
Structure — Functions doing multiple things. Files with mixed responsibilities. Duplicated logic. Complex conditionals that could be simplified.
Dead code — Unused imports. Unreachable branches. Functions nothing calls. Commented-out code.
Find, fix, test. One issue at a time. If tests fail, revert and note why.
Not architecture review, not larp detection. Don't change behavior. "No issues found" is valid.
## Fixes Applied
### 1. {path}:{line} - {category}
BEFORE: {old code}
AFTER: {new code}
REASON: Why this was changed
## Skipped (tests failed)
- {path}:{line} - what you tried, why it broke tests
## Summary
- Fixed: N issues
- Skipped: M issues (would break tests)
- Lines removed: K