bootstrap-knowledge
Skill2 starsChanged 19 days agoApache-2.0View on GitHub
Scan a project and generate comprehensive knowledge for all personas. Creates semantic vector index, deep analysis, file watcher. Use when user says "bootstrap knowledge", "learn architecture", or "scan project structure".
In this repository124 other files it gives its agents.
- add-projectSkill
- ansible-configure-vmSkill
- api-smoke-testSkill
- appinterface-checkSkill
- attach-session-to-jiraSkill
- aws-rds-debugSkill
- beerSkill
- bootstrap-all-knowledgeSkill
- build-persona-styleSkill
- cancel-pipelineSkill
- cert-checkSkill
- check-ci-healthSkill
- check-integration-testsSkill
- check-mr-feedbackSkill
- check-my-prsSkill
- check-secretsSkill
- ci-retrySkill
- cleanup-branchesSkill
- cleanup-stale-executionsSkill
- clone-jira-issueSkill
- close-issueSkill
- close-mrSkill
- cloud-inventorySkill
- coffeeSkill
- compare-optionsSkill
- create-jira-issueSkill
- create-mrSkill
- create-slide-deckSkill
- data-migration-verifySkill
- debug-local-dbSkill
- debug-prodSkill
- deploy-to-ephemeralSkill
- dev-workflow-orchestratorSkill
- discovered-work-summarySkill
- edit-slide-deckSkill
- email-digestSkill
- environment-overviewSkill
- explain-codeSkill
- export-presentationSkill
- extend-ephemeralSkill
- find-similar-codeSkill
- gather-contextSkill
- gdrive-researchSkill
- gke-cluster-opsSkill
- hello-worldSkill
- hotfixSkill
- inscope-researchSkill
- investigate-alertSkill
- investigate-service-issuesSkill
- investigate-slack-alertSkill
- jira-hygiene-allSkill
- jira-hygieneSkill
- knowledge-refreshSkill
- konflux-statusSkill
- learn-architectureSkill
- learn-patternSkill
- list-presentationsSkill
- local-build-testSkill
- local-dev-environmentSkill
- manage-local-servicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If not provided: detect from cwd via config.json repositories
- Distinctive: line 39
Only if vector index created successfully
- Distinctive: line 44
Read README.md (first 5000 chars)
- Very specific: line 53
If "permission denied": learn_tool_fix("code_index", "permission denied", "Cannot write to vector cache", "Check …
- Distinctive: line 54
If "out of memory": learn fix for memory
- Distinctive: line 55
If "already running": note watcher is active
- Distinctive: line 59
Update state/knowledge with project, last_bootstrap, vector_indexed
≈ “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
Bootstrap Knowledge - Build Project Knowledge
Scans project, generates persona-specific knowledge, creates vector index for code search.
Inputs
| Input | Type | Default | Purpose |
project | string | auto | Project from config.json (auto from cwd) |
personas | string | "developer,devops,tester,release" | Comma-separated |
deep_scan | bool | false | Deeper analysis (slower) |
create_vector_index | bool | true | Create semantic code index |
start_watcher | bool | true | Auto-update index on file changes |
Workflow
1. Detect Project
- If not provided: detect from cwd via config.json repositories
- Validate project exists in config and path exists
2. Check Known Issues
check_known_issues("code_index", "")- vector indexing issues
3. Knowledge Scan per Persona
- For each in personas_list:
knowledge_scan(project, persona, force=false) - Personas: developer, devops, tester, release
4. Create Vector Index
code_index(project)- semantic embeddings for code search- Parse result: files indexed, chunks created
5. Start File Watcher
code_watch(project, action="start")- auto-reindex on changes- Only if vector index created successfully
6. Deep Scan (if enabled)
code_search(query="class definition pattern implementation", project, limit=10)code_search(query="exception handling try except raise error", project, limit=5)- Read README.md (first 5000 chars)
- Scan tests/ for test_*.py, *.test.js, conftest.py
7. Build Summary
- List generated files:
memory/knowledge/personas/<persona>/<project>.yaml - Vector index stats: files, chunks, watcher status
- Deep scan: README length, test counts, patterns, error handlers
8. Learn from Failures
- If "permission denied":
learn_tool_fix("code_index", "permission denied", "Cannot write to vector cache", "Check ~/.cache/aa-workflow/vectors/") - If "out of memory": learn fix for memory
- If "already running": note watcher is active
9. Log and Track
memory_session_log("Bootstrapped knowledge for <project>", "Personas: X, Vector: Y")- Update state/knowledge with project, last_bootstrap, vector_indexed
10. Output Format
## 📚 Knowledge Bootstrap Complete: <project>
**Project Path:** `path`
**Personas:** developer, devops, tester, release
### Generated Knowledge Files
- memory/knowledge/personas/developer/<project>.yaml
- ...
### 🔍 Vector Index Created
- Files indexed: N
- Chunks created: N
- File watcher: ✅ Running
### Next Steps
1. knowledge_query(project='...', persona='developer')
2. code_search(query='...', project='...')
3. knowledge_update() for gotchasKey Details
- Chains to:
knowledge_refresh,learn_architecture - Provides context for:
gather_context,review_pr,start_work - Project path from config.json repositories
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.

