brain-approve
Approve, reject, or manage pending brain memories. Use: /brain-approve [all|<id>]
Query the claude-teams-brain for context about a specific role or topic
$ npx -y skills add Gr122lyBr/claude-teams-brain --skill brain-query --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/brain-queryContext preview
The summary Claude sees to decide when to auto-load this skill.
Query the claude-teams-brain for context about a specific role or topic
name: brain-query description: | Query the claude-teams-brain for context about a specific role or topic user_invocable: true
Preview exactly what memory a new teammate would receive when they spawn. Useful for debugging memory, verifying a role has context, or understanding what the brain knows before starting a session.
The user provides a role name as an argument (e.g. `/brain-query backend`).
Run:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/brain_engine.py query-role "$ARGS" "$CLAUDE_PROJECT_DIR"Display the returned context in a readable format, showing:
Use the same names as your agent teammates. Common roles:
| Role | Use for | |------|---------| | `backend` | API, server logic, middleware | | `frontend` | UI, React/Vue components, CSS | | `database` | Schema, migrations, queries | | `tests` | Unit, integration, e2e tests | | `devops` | Docker, CI/CD, deployment | | `security` | Auth, permissions, encryption | | `architect` | System design, refactoring |
The brain also auto-infers roles from task descriptions — an agent with no explicit role that worked on React components will have its memory tagged as "frontend" automatically.
Suggest: 1. Running an Agent Team session with a teammate using this role name 2. Using `/brain-remember` to manually seed rules for this role 3. Using `/brain-seed <profile>` to load stack conventions
Give your Claude Code Agent Teams a memory. Auto-injects role-specific context into every new teammate — your team never starts blind again.
Repo: Gr122lyBr/claude-teams-brain
Approve, reject, or manage pending brain memories. Use: /brain-approve [all|<id>]
Launch the brain dashboard web UI to visualize and curate memories, decisions, and files. Trigger: /brain-dashboard
Export accumulated brain knowledge as a CONVENTIONS.md file in your project. Distills all rules, decisions, files, and agent roles into a committable file.
Remove a manually stored memory from the brain by partial text match. Use: /brain-forget <text>
Export accumulated brain knowledge as `CONVENTIONS.md` and open a GitHub PR so your whole team can review what the AI team learned.