We split this skill into the rules it gives an agent

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

• 0

  Common

  Most of the 44 edited versions we read keep these.

• 2

  Distinctive

  This author's own choices. Worth a look.

• 4

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Run git branch --show-current and confirm the current branch is changeset-release/main.

   line 14
2. Distinctive:

   Read all 8 files in parallel.

   line 29
3. Very specific:

   Use the Edit tool to update the constant to match the package.json version.

   line 37
4. Very specific:

   If all version.ts files already match their package.json versions, note that no updates were needed.

   line 40
5. Very specific:

   Run pnpm install from the repo root to update the lock file.

   line 46
6. Distinctive:

   Commit any changes that were just made.

   line 60

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

  Word for word · 0

  None found.

  Edited · 0

  None found.

  Wrote their own version · 45

  1. CherryHQ/cherry-studio★ 53ksame name
  2. redis/go-redis★ 22ksame name
  3. joke2k/faker★ 19ksame name
  4. pybind/pybind11★ 18ksame name
  5. telepresenceio/telepresence★ 7.3ksame name
  6. modelcontextprotocol/csharp-sdk★ 4.6ksame name
  7. CLIUtils/CLI11★ 4.5ksame name
  8. tmoroney/auto-subs★ 4.3ksame name
  9. ethereum/consensus-specs★ 4ksame name
  10. kube-hetzner/terraform-hcloud-kube-hetzner★ 3.9ksame name

  35 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 sync-docs, review-change and 5 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.

  • Eipi-TongSkill

    sync-docs

    Update SPEC.md and docs/DECISIONS.md to reflect recent code changes. Use after completing a feature, or when the user says "sync docs", "update the spec", or "log this decision".

    Also in 4 projects that use this

  • thlaureSkill

    review-change

    Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.

    Also in 3 projects that use this

  • kiminmonacoSkill

    implement-feature

    Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers

    Also in 3 projects that use this

  • DockerSkill

    fix-issue

    Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR. Use when asked to fix an issue: "fix issue 1234", "resolve #500", "create a PR for issue 200".

    Also in 3 projects that use this

  • DockerSkill

    review-pr

    Review one or more incoming Docker documentation pull requests as a maintainer. Independently validate technical claims, assess editorial fit and information architecture, choose a verdict, and draft exact inline or PR-wide feedback behind a confirmation gate. Use for requests such as "review PR 123", "is this PR correct?", "does this information belong here?", "validate this PR", or "help review backlog PRs". Do not use to maintain or fix a PR you own; use maintain-pr for that.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

• In this repository5 other files it gives its agents.

  • adding-api-versionsSkill
  • fix-broken-major-upgradeSkill
  • list-broken-major-upgradesSkill
  • investigating-github-issuesSkill
  • reviewing-pull-requestsSkill