repo-intake
Skill192 starsChanged 39 days agoMITView on GitHub
Project initialization inventory (one-time). Use when: first onboarding a project, rebuilding cache after structural changes. Not for: day-to-day development (read cache directly), finding specific files (use code-explore). Output: project map with entrypoints + test map + next steps.
3 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- AuroraBackcountry/agent-configtheir own version, first seen Nov 1, 2026
- hmj1026/dhpkedited, first seen Nov 1, 2026
- sd0xdev/sd0x-harnessword for word, first seen Oct 6, 2026
Other versions3 projects use a version of this.
Word for word · 1
- sd0xdev/sd0x-harness★ 192100% same
Edited · 1
- hmj1026/dhpk★ 268% same
Wrote their own version · 1
- AuroraBackcountry/agent-config★ 1same 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 repository102 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adrSkill
- agentctl-setupSkill
- architectureSkill
- askSkill
- best-practicesSkill
- bug-fixSkill
- bump-versionSkill
- check-coverageSkill
- claude-healthSkill
- code-exploreSkill
- code-investigateSkill
- codex-architectSkill
- codex-brainstormSkill
- codex-cli-reviewSkill
- codex-code-reviewSkill
- codex-explainSkill
- codex-implementSkill
- codex-review-branchSkill
- codex-review-docSkill
- codex-review-fastSkill
- codex-reviewSkill
- codex-securitySkill
- codex-setupSkill
- codex-test-genSkill
- codex-test-reviewSkill
- contract-decodeSkill
- create-prSkill
- create-requestSkill
- de-ai-flavorSkill
- debugSkill
- deep-analyzeSkill
- deep-exploreSkill
- deep-researchSkill
- dep-auditSkill
- deploy-flowSkill
- dev-security-auditSkill
- doc-refactorSkill
- doc-reviewSkill
- epic-mergeSkill
- feasibility-studySkill
- feature-devSkill
- feature-verifySkill
- fp-briefSkill
- generate-runnerSkill
- gh-stackSkill
- git-investigateSkill
- git-profileSkill
- install-hooksSkill
- install-rulesSkill
- install-scriptsSkill
- issue-analyzeSkill
- jiraSkill
- load-pr-reviewSkill
- merge-prepSkill
- necessity-auditSkill
- next-stepSkill
- obsidian-cliSkill
- op-sessionSkill
- orchestrateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Only need to find specific files (use Glob/Grep)
- Very specific: line 103
Test Map covers Unit/Integration/E2E layers
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repo Intake
When to Use
- First time onboarding a project
- Rebuilding cache after major project structural changes
- Cache expired, needs updating
When NOT to Use
- Already familiar with project structure (read cache directly)
- Only need to find specific files (use Glob/Grep)
- Day-to-day development (cache already exists)
Workflow
Docs -> Entrypoints -> Tests Map -> Next StepsUsage
bash scripts/run-skill.sh repo-intake intake_cached.js --mode auto --top 10Manifest Map(宣告依賴地圖)
Monorepo / multi-package repo 的 workspace 拓撲與宣告依賴圖。邊語義是
declares_dependency——manifest 裡寫了什麼,不證明 import、呼叫或 runtime 影響。
一律 fail-closed:整份檔案無法讀取/UTF-8 解碼、或 JSON document 無法解析則記
coverage skipped;已進入 Go/TOML recognizer 的相關不支援 construct 則記
partial。絕不產生猜測邊。
bash scripts/run-skill.sh repo-intake manifest_map.js # overview (md)
bash scripts/run-skill.sh repo-intake manifest_map.js --format json # 完整 envelope
bash scripts/run-skill.sh repo-intake manifest_map.js --reverse <selector> # 誰宣告依賴它
bash scripts/run-skill.sh repo-intake manifest_map.js --cycles # 宣告環偵測| Flag | 說明 |
--format md|json | 預設 md;json 為完整 artifact,不受 --top 截斷 |
--top N | md 清單截斷(預設 12) |
--reverse <sel> | selector:節點 ID(ws:node:packages/a)或名稱(node:lodash / lodash);多重匹配 exit 2 並列出候選 |
--cycles | 與 --reverse 互斥 |
--include-candidates | 把未經 controller 確認的 candidate workspace 納入架構節點集(預設排除) |
生態系:node / php / go / rust / python(辨識 manifest 見
scripts/config/repo-intake.json 的 manifest_map 段)。無效參數 exit 2。
資料模型、解析矩陣與凍結語法契約:references/manifest-map.md;完整規格:
docs/features/repo-intake-manifest-map/2-tech-spec.md。
Cache Location
Cache stored at: ~/.claude/cache/repo-intake/<repoKey>/
| File | Description |
latest.md | Latest scan results |
latest.json | Latest scan results (JSON) |
LATEST.json | Cache metadata |
Output
## Overview
<summary>
## Entrypoints
- {CONFIG_FILE}
- {BOOTSTRAP_FILE}
## Test Map
| Type | Pattern |
| ----------- | ----------------- |
| Unit | test/unit/ |
| Integration | test/integration/ |
| E2E | test/e2e/ |
## Next Steps
- <questions>Verification
- Output includes Overview, Entrypoints, Test Map, Next Steps
- Entrypoints correctly identify
{CONFIG_FILE},{BOOTSTRAP_FILE} - Test Map covers Unit/Integration/E2E layers
References
references/manifest-map.md— Manifest map 資料模型、解析矩陣、凍結契約摘要references/archived/MIDWAY_HEURISTICS.md— Legacy MidwayJS heuristics (archived, for reference only)
Scripts
| Script | Purpose |
scripts/intake_cached.js | Main intake with caching |
scripts/scan_repo.js | Full repo scanner (framework-agnostic) |
scripts/scan_delta.js | Delta scan for changed files |
scripts/manifest_map.js | Workspace 拓撲 + 宣告依賴圖(overview / reverse / cycles) |
Examples
Input: /repo-intake
Action: Execute intake script -> Output project mapInput: /repo-intake save
Action: Execute intake script -> Output and write to docs/ai/intake/Does 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.

