Loading...
Loading...
Found 64 Skills
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).
Comprehensive code review with parallel specialist sub-agents. Analyzes requirements traceability, code quality, security, performance, accessibility, test coverage, and technical debt. Produces detailed findings and calls /qa-gate for final gate decision.
System health check (MOT) for skills, agents, hooks, and memory
Create custom linting rules for markdownlint including rule structure, parser integration, error reporting, and automatic fixing.
Automated fix skill that reads review reports and applies fixes to ADR documents - handles broken links, element IDs, missing files, and iterative improvement
Comprehensive content review and quality assurance for BRD documents - validates link integrity, requirement completeness, strategic alignment, and identifies issues requiring manual attention
Check documents against style rules and fix violations. Use after writing or editing documents to ensure compliance with document-writing and text-formatting-ja rules.
Review InboxMate demos waiting for QA. Finds CRM opportunities at SCREENING with demoStatus=PENDING_REVIEW, opens each demo link, checks quality, and flags as OK_TO_SEND or NEEDS_FIX with a note explaining why.
Diagnose and fix oh-my-codex installation issues
Scans the current project's frontend files, finds the components most out of alignment with .marrow.md, and fixes them automatically — without the user specifying a target. The zero-argument soul alignment sweep. Use this skill when the user wants to broadly align the project to the design soul, fix whatever is most off without specifying a file, or run a soul sweep across multiple components at once. Triggers on: /marrow-magic, or prompts like "fix everything to match marrow", "align my whole project", "soul sweep", "fix the worst violations", "everything feels off", "clean up all components to match the design". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.
Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills.
Monitors a PR's CI checks and review comments until all pass and issues are resolved. Use when watching CI status, waiting for checks to pass, or fixing CI errors on a pull request.