We split this skill into the rules it gives an agent

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

• 0

  Common

  Most of the 47 edited versions we read keep these.

• 3

  Distinctive

  This author's own choices. Worth a look.

• 3

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   When the user asks you to create a branch, commit changes, and create a github pull request based on their current working directory or …

   line 20
2. Distinctive:

   Run git status, git diff, and git diff --staged in the terminal to inspect what has changed.

   line 23
3. Very specific:

   Important: When formatting the commit message, fetch and strictly follow the comprehensive guidelines from the online reference using the …

   line 26
4. Distinctive:

   Use terminal commands to checkout the new branch, stage the changes, commit, and push to origin.

   line 29
5. Very specific:

   Use the gh CLI to open the PR on GitHub.

   line 33
6. Very specific:

   If gh pr create returns an authorization error, kindly ask the user to run gh auth login to authenticate.

   line 38

“Common” is measured: kept by at least 6 in 10 of the 47 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. samchon/typia★ 6ksame name
  2. epicenter-md/epicenter★ 4.8ksame name
  3. EpicenterHQ/epicenter★ 4.8ksame name
  4. werf/werf★ 4.7ksame name
  5. basicmachines-co/basic-memory★ 4.4ksame name
  6. PaulWoitaschek/Voice★ 3.2ksame name
  7. event-catalog/eventcatalog★ 3ksame name
  8. heyitsnoah/claudesidian★ 2.6ksame name
  9. samchon/nestia★ 2.2ksame name
  10. theopenco/llmgateway★ 1.7ksame 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 issue-campaign, development 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.

  • samchonSkill

    issue-campaign

    Defines the default solo repository-wide issue campaign for typia: exhaustive discovery, lead-vetted issue publication, one unified CI-validated implementation pull request per cycle, solo Self-Review, and repeated rediscovery until a full clean round. Use for broad audits, many issue candidates, or repeated issue-to-pull-request campaigns unless the user explicitly requests parallel or multi-agent execution; do not use for one already-defined issue or an ordinary pull request.

    Also in 3 projects that use this

  • mfang0126Skill

    development

    Full-stack development workflow skill. Guides the complete cycle from understanding requirements to shipping code via PR with Preview validation.

    Also in 3 projects that use this

  • AnthropicSkill

    contracts

    Answer a question across a corpus of contract documents with verified citations. Use when the user asks what a contract says, which contracts have a clause, what changed between amendments, or any question that needs reading and citing across a set of contract files. The corpus must be on the local filesystem (see README).

    Also in 3 projects that use this

  • dragonflydbSkill

    benchmark

    Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

    Also in 4 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 6 projects that use this

  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 5 projects that use this

• In this repository9 other files it gives its agents.

  • agent-loopSkill
  • codebase-context-generatorSkill
  • code-reviewSkill
  • manual-automationSkill
  • planning-and-task-breakdownSkill
  • project-change-intelligenceSkill
  • slack-cliSkill
  • test-driven-developmentSkill
  • yt-random-comment-pickerSkill