run-tests

We split this skill into the rules it gives an agent

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

• 0

  Common

  Most of the 41 edited versions we read keep these.

• 1

  Distinctive

  This author's own choices. Worth a look.

• 1

  Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 41 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. netbox-community/netbox★ 22ksame name
  2. yagop/node-telegram-bot-api★ 9.2ksame name
  3. gitextensions/gitextensions★ 8.6ksame name
  4. ethereum/consensus-specs★ 4ksame name
  5. dotnet/sdk★ 3.2ksame name
  6. ComplianceAsCode/content★ 2.8ksame name
  7. idaholab/moose★ 2.4ksame name
  8. CliMA/Oceananigans.jl★ 1.4ksame name
  9. microsoft/testfx★ 1.1ksame name
  10. serenedb/serenedb★ 955same 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 prepare-release, commit 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.

  • 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

  • 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

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 5 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 5 projects that use this

• In this repository11 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • api-endpointsSkill
  • backend-architectureSkill
  • code-commentsSkill
  • data-workshopSkill
  • engineering-tasteSkill
  • finetuning-model-onboardingSkill
  • frontend-designSkill
  • mcpSkill
  • pr-etiquetteSkill
  • seed-demo-dataSkill