NeVibe · 8
Code review and refactoring: skills, rules and MCP servers
Code review and refactoring for Claude Code, Codex and Cursor: skills, subagents, rules and MCP servers, from popular to niche.
improve-codebase-architectureskill This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review.
tddskill Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details.
triageskill This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue.
codebase-designskill This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write.
code-reviewskill Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress.
implementskill Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine.
to-ticketsskill Turns a plan, spec, or conversation into linked tickets with blocking dependencies. Use it when work needs to be handed to agents or published to a tracker.
migrate-to-shoehornskill Replaces `as` type assertions in tests with helpers from `@total-typescript/shoehorn`. Use it when tests need partial objects or deliberately invalid data.
Code review and refactoring: the agent reads a diff, hunts for bugs, duplication and needless complexity, and suggests simplifications. Subagents shine here, since a reviewer with its own context does not carry the edit history and reads the code fresh. When choosing, check what the skill does with its findings: write a report or edit files straight away. The second is convenient and risky in a shared repository.
