repo-context
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when a request starts with scanning the Hussh repository, establishing repo context, mapping code/docs/skills, or deciding which owner skill should own the next step.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- aymardkouakou/claude-gh-skillstheir own version, first seen Nov 8, 2026
- pfangueiro/claude-code-agentstheir own version, first seen Nov 8, 2026
- justEstif/pi-shelftheir own version, first seen Oct 13, 2026
- Chris-Carruthers/canontheir own version, first seen Aug 29, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- pfangueiro/claude-code-agents★ 7same name
- Chris-Carruthers/canon★ 4same name
- aymardkouakou/claude-gh-skills★ 1same name
- justEstif/pi-shelf★ 0same name
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.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 0 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with frontend, backend, security-audit, and docs-governance.
- Very specific: line 56
Run summary first to get owners, spokes, surface coverage, and uncovered surfaces.
- Very specific: line 58
Use list-workflows and route-task <workflow-id> when the request matches a recurring execution shape.
- Very specific: line 59
Use data-model-audit before data-model implementation when migration/table classification, retention posture, or legacy write drift is in …
- Very specific: line 60
Use impact <workflow-id> before implementation when blast radius, docs, or verification scope is unclear.
- Very specific: line 61
Keep the first pass compact by default.
- Very specific: line 62
Use --text when a human-readable low-token routing summary is enough.
- Very specific: line 64
Use validate or audit when changing the taxonomy, coverage map, workflow packs, or skill-routing docs.
- Very specific: line 65
Treat low-severity context-size and modularity findings from audit as review-required signals only.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
Hussh Repo Context Skill
Purpose and Trigger
- Primary scope:
repo-context-intake - Trigger on broad repository scans, cross-domain mapping, surface discovery, and choosing the correct owner skill before implementation work starts.
- Avoid overlap with
frontend,backend,security-audit, anddocs-governance.
Coverage and Ownership
- Role:
owner - Owner family:
repo-context
Owned repo surfaces:
README.mddata
Non-owned surfaces:
frontendmobile-nativebackendsecurity-auditdocs-governancerepo-operationsanalytics-observability-governance
Do Use
- First-pass repository orientation before any narrower implementation workflow.
- Mapping the full skill taxonomy and the meaningful repo surface coverage.
- Routing recurring work into explicit workflow packs and impact bundles.
- Finding code/docs/skill drift or orphaned areas in the repository map.
- Running the data-model audit workflow when table-family drift, migration classification, or runtime DB ownership is the starting question.
Do Not Use
- Narrow work that is already clearly inside a domain owner skill.
- Docs-only governance once the correct docs home is already obvious.
- Deep product, ops, or security implementation work.
Read First
.agents/skills/repo-context/references/index-contract.md.agents/skills/repo-context/references/ownership-map.mddocs/development/repository-map.md
Workflow
- Run
summaryfirst to get owners, spokes, surface coverage, and uncovered surfaces. - Open exactly one deeper section next:
docs,frontend,backend,skills, orcommands. - Use
list-workflowsandroute-task <workflow-id>when the request matches a recurring execution shape. - Use
data-model-auditbefore data-model implementation when migration/table classification, retention posture, or legacy write drift is in scope. - Use
impact <workflow-id>before implementation when blast radius, docs, or verification scope is unclear. - Keep the first pass compact by default; use
--verboseonly when a heavy section such asskillsorbackendneeds deeper inspection. - Use
--textwhen a human-readable low-token routing summary is enough. - Route the task into the recommended owner skill as soon as the domain is clear.
- Use
validateorauditwhen changing the taxonomy, coverage map, workflow packs, or skill-routing docs. - Treat low-severity context-size and modularity findings from
auditas review-required signals only; do not split files or add folders unless a bounded owner, workflow, or navigation problem is proven.
Handoff Rules
- Route broad frontend work to
frontend, native work tomobile-native, backend work tobackend, trust and audit work tosecurity-audit, docs work todocs-governance, analytics observability work toanalytics-observability-governance, and generic ops work torepo-operations. - Route licensing and notice-governance work to
oss-license-governance. - Route bootstrap, devcontainer, doctor, and contributor-first-run work to
contributor-onboarding. - Route optional-mirror sync and subtree-governance work to
subtree-upstream-governance. - Route skill-system work to
codex-skill-authoring. - Route board workflows to
planning-boardand public/community reply work tocomms-community.
Required Checks
./bin/hushh agents scan summary
./bin/hushh agents list-workflows
./bin/hushh agents route-task repo-orientation
./bin/hushh agents impact repo-orientation
./bin/hushh agents data-model-audit
./bin/hushh agents audit
python3 .agents/skills/repo-context/scripts/repo_scan.py validate
python3 .agents/skills/repo-context/scripts/architecture_fitness.py --self-test && python3 .agents/skills/repo-context/scripts/architecture_fitness.py --limit 20Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

