review-changes

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

• 0

  Common

  Most of the 28 edited versions we read keep these.

• 2

  Distinctive

  This author's own choices. Worth a look.

• 0

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Distinctive:

   Run git status to see what's changed

   line 8
2. Distinctive:

   Run git diff to see the actual changes

   line 9

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

• Other versions29 projects use a version of this.

  Word for word · 0

  None found.

  Edited · 0

  None found.

  Wrote their own version · 29

  1. tirth8205/code-review-graph★ 32ksame name
  2. docker/docs★ 4.7ksame name
  3. microsoft/nvx★ 803same name
  4. blockscout/frontend★ 309same name
  5. timothywarner-org/claude-code★ 223same name
  6. appclawhq/AppClaw★ 111same name
  7. uniffy-io/uniffy★ 68same name
  8. munvard/dockterm★ 48same name
  9. jjxmonster/skills★ 8same name
  10. Arasz/ai-badger★ 3same name

  19 more not listed

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• Used alongsideProjects with it also use explore-codebase, debug-issue and 3 more.

  Other files people use alongside this one.

  How we pick theseFiles found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

  • srclightSkill

    explore-codebase

    This skill should be used when the user asks to "explore this codebase", "understand this project", "give me an overview", "how does this work", "onboard me", "walk me through the architecture", "map the codebase", or any request to understand a codebase's structure, architecture, or design.

    Also in 4 projects that use this

  • NVIDIASkill

    debug-issue

    Use when the user asks to debug, investigate, or fix a GitHub issue or supplies a repository bug report.

    Also in 4 projects that use this

  • srclightSkill

    refactor-safely

    This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.

    Also in 4 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

• In this repository8 other files it gives its agents.

  • CLAUDE.mdCLAUDE.md
  • commit-push-prSkill
  • grillSkill
  • quick-commitSkill
  • sync-claude-configSkill
  • techdebtSkill
  • test-and-fixSkill
  • worktreeSkill