We split this skill into the rules it gives an agent

16 rules. 0 are common, 12 are distinctive, and 4 are very specific to this project.

• 0

  Common

  Most of the 167 edited versions we read keep these.

• 12

  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. Distinctive:

   Run this before every commit to ensure code quality and security.

   line 8
2. Distinctive:

   Before creating a commit

   line 12
3. Distinctive:

   Before pushing to remote

   line 13
4. Distinctive:

   After making significant code changes

   line 14
5. Distinctive:

   When asked to "verify", "check", or "validate" the code

   line 15
6. Distinctive:

   Run all steps in order. Stop on first failure.

   line 19
7. Distinctive:

   If there are auto-fixable issues:

   line 27
8. Distinctive:

   If formatting is needed:

   line 39
9. Distinctive:

   All tests must pass. Review coverage for newly added code.

   line 51
10. Distinctive:

    Before committing, check for these security concerns specific to this project:

    line 55
11. Very specific:

    No shell=True: Search for shell=True in any subprocess call — this is forbidden

    line 57
12. Very specific:

    No hardcoded secrets: Search for patterns like token, secret, password, api_key with string literal values

    line 58
13. Very specific:

    Subprocess arguments: All user input passed to Claude CLI must use -- separator

    line 60
14. Distinctive:

    Verify the public API still works:

    line 70
15. Distinctive:

    Security failures: STOP. Do not commit. Fix the vulnerability first

    line 80
16. Very specific:

    Import failures: Check __init__.py exports match actual module structure

    line 81

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

  Word for word · 1

  1. ebibibi/ebi-agent-chat-relay★ 66100% same

  Edited · 0

  None found.

  Wrote their own version · 187

  1. react/react★ 252ksame name
  2. facebook/react★ 252ksame name
  3. garrytan/gstack★ 139ksame name
  4. oven-sh/bun★ 96ksame name
  5. anthropics/financial-services★ 41ksame name
  6. anthropics/financial-services-plugins★ 41ksame name
  7. Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
  8. Yeachan-Heo/oh-my-claudecode★ 40ksame name
  9. anthropics/claude-quickstarts★ 19ksame name
  10. NVIDIA-NeMo/Speech★ 19ksame name

  177 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 external-context, instinct-export 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.

  • Jurel89Skill

    external-context

    Invoke parallel document-specialist agents for external web searches and documentation lookup

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 5 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • AaravChadhaSkill

    secure

    Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.

    Also in 3 projects that use this

• In this repository9 other files it gives its agents.

  • AGENTS.mdAGENTS.md
  • .github/copilot-instructions.mdCopilot instructions
  • add-cogSkill
  • python-qualitySkill
  • releaseSkill
  • security-auditSkill
  • tddSkill
  • test-guideSkill
  • relay-thread-managerSkill