Index of every page on this site: llms.txt

Review and refactoring

You read other devs' code and reshape it without breaking it.

Teach your agent skilld

npx skilld install skilld --global
Adds the skilld Skill to your agent for every project.

73 skills

Hand-picked review and refactoring skills

Turn review comments, bot findings, and production issues into fixed code.

  1. /resolve-agent-reviews

    Resolve PR review bot findings on current PR. Fetches unanswered bot comments, evaluates each finding, fixes real bugs, dismisses false positives, replies to every comment, and waits for the head commit's checks until a pass is clean.

    329 GitHub stars
  2. /requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    323k GitHub stars
  3. /fix-sentry-issues

    Use Sentry MCP to discover, triage, and fix production issues with root-cause analysis. Use when asked to fix Sentry issues, triage production errors, investigate error spikes, or clean up Sentry noise. Requires Sentry MCP server. Triggers on "fix sentry", "triage errors", "production bugs", "sentry issues".

    380 GitHub stars
  4. /receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    323k GitHub stars
  5. Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".

    4k GitHub stars
  1. /refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    41k GitHub stars

More review and refactoring skills, ranked by GitHub stars

  1. /code-review

    Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

    329k GitHub stars
  2. /migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    329k GitHub stars
  3. /pr

    Use when writing a PR body.

    329k GitHub stars
  4. /compiler-port

    Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.

    253k GitHub stars
  5. /compiler-review

    Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.

    253k GitHub stars
  1. /fix

    Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

    253k GitHub stars
  2. /verify

    Use when you want to validate changes before committing, or when you need to check all React contribution requirements.

    253k GitHub stars
  3. Checks if a community pull request is ready for human review. Verifies CLA signature, PR title format, description completeness, test coverage, and cubic-dev-ai issues, then triages to the right Linear team or recommends a close. Use when given a PR number or branch name to review, or when the user says /community-pr-readiness-check, or asks to check if a PR is ready for review.

    211k GitHub stars
  4. /create-pr

    Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.

    211k GitHub stars
  5. /gh-stack

    Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.

    211k GitHub stars
  6. /migrate-module

    Plans and carries out the move of a backend module from packages/cli/src/modules/<name> into its own workspace package at packages/modules/<name>/backend. Use when the user wants to extract, migrate or package a backend module, remove cli dependencies from a module, or move a cli service into @n8n/backend-services so that modules can use it.

    211k GitHub stars
  7. /create-pr

    Create Git branches, commits, pushes, and GitHub pull requests for Next.js. Use when the user asks to create a branch, commit current changes, open a PR or draft PR, publish a pull request, or recover from gh pr create / PR template issues. Covers .github/pull_request_template.md, --body formatting, <agent-name>/ branch names, and Codex app git directives.

    144k GitHub stars
  8. /autoplan

    Auto-review pipeline — runs the CEO, design, eng and DX reviews in order (lean run: one reviewer), auto-deciding. Use for: run all reviews, automatic review pipeline. (gstack)

    142k GitHub stars
  9. /codex

    OpenAI Codex CLI wrapper — three modes. Use for: codex review, second opinion, outside voice challenge. (gstack)

    142k GitHub stars
  10. /deslop-shared-libs

    Find worthwhile shared-code extractions in recent work. Use for: find code worth sharing. (gstack)

    142k GitHub stars

Other tracks