Auto-learn project conventions from git history — zero manual setup. Trigger: /brain-learn
Scanned 5/27/2026
Install via CLI
openskills install Gr122lyBr/claude-teams-brain---
name: brain-learn
description: |
Auto-learn project conventions from git history — zero manual setup.
Trigger: /brain-learn
user_invocable: true
---
# brain-learn
Scan the repo's git history and automatically extract conventions, architecture signals, file coupling patterns, and code hotspots. The brain teaches itself from your repo — no manual `/brain-remember` needed.
## Instructions
Run:
```
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/brain_engine.py learn "$CLAUDE_PROJECT_DIR"
```
Parse the JSON response which contains:
- `status` — "ok" or "error"
- `commits_analyzed` — number of commits scanned (up to 200)
- `conventions_found` — total conventions detected
- `conventions_added` — new conventions stored (excludes duplicates)
- `conventions_skipped` — conventions already in the brain
- `file_couplings` — number of file coupling patterns found
- `hotspots` — number of hotspot entries (files + directories)
- `conventions` — list of convention strings that were added
- `message` — human-readable summary
Display results grouped by category:
```
## Learned from Git History
**Commits analyzed**: 187
### Conventions Added (6 new, 2 already known)
- Convention: commit messages use Conventional Commits — common scopes: api, auth, db
- Convention: branches use prefix naming (feature/, fix/, chore/)
- Architecture: primary stack is TypeScript (Node.js)
- Architecture: CI/CD uses GitHub Actions
- Architecture: uses Docker for containerization
- Convention: tests use *.test.ts naming
### Also Indexed
- 12 file coupling patterns (searchable via `/brain-search coupling`)
- 23 code hotspots (searchable via `/brain-search hotspots`)
```
After displaying results, suggest:
> **Next steps:**
> - `/brain-search coupling` — see which files change together
> - `/brain-search hotspots` — see the most active files
> - `/brain-status` — verify the brain state
> - `/brain-forget <text>` — remove any convention that doesn't apply
The command is idempotent — running it again only adds net-new findings.
**Important**: Only use the exact command shown above. Do not invent or guess other command names.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.