fix-issue

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

• 0

  Common

  Most of the 50 edited versions we read keep these.

• 4

  Distinctive

  This author's own choices. Worth a look.

• 1

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Search the codebase for the affected area.

   line 10
2. Distinctive:

   Write a failing test that reproduces the bug first.

   line 11
3. Distinctive:

   Run the affected package tests, then lint.

   line 14
4. Very specific:

   Add a fragment under changelog.d/ (format in changelog.d/README.md.

   line 15
5. Distinctive:

   Never tag a release from this workflow — releases follow the flow in CLAUDE.md and are Vincent's call.

   line 18

“Common” is measured: kept by at least 6 in 10 of the 50 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 versions52 projects use a version of this.

  Word for word · 0

  None found.

  Edited · 0

  None found.

  Wrote their own version · 52

  1. pytorch/pytorch★ 105ksame name
  2. ZhuLinsen/daily_stock_analysis★ 67ksame name
  3. Dokploy/dokploy★ 38ksame name
  4. remix-run/remix★ 33ksame name
  5. jlowin/fastmcp★ 28ksame name
  6. PrefectHQ/fastmcp★ 28ksame name
  7. NVIDIA-NeMo/NeMo★ 19ksame name
  8. NVIDIA-NeMo/Speech★ 19ksame name
  9. getsentry/sentry-javascript★ 8.8ksame name
  10. datlechin/TablePro★ 6.3ksame name

  42 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 document, write-tests and 10 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.

  • nicolasestremSkill

    document

    Create focused documentation for specific components or features

    Also in 4 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 4 projects that use this

  • ShopifySkill

    prepare-release

    Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install

    Also in 3 projects that use this

  • GitHubSkill

    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.

    Also in 5 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    build

    Build the TypeSpec Rust emitter from source. Run this after cloning the repo, after pulling changes, or when TypeScript source files have been modified.

    Also in 4 projects that use this

• In this repository10 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • CLAUDE.mdCLAUDE.md
  • autofixSkill
  • commitsSkill
  • discord-reportsSkill
  • prsSkill
  • smoke-testingSkill
  • tag-releaseSkill
  • testingSkill
  • triageSkill