Agent Claude Code
Use proactively after a logical chunk of code is written or before opening a PR, to review the diff for correctness bugs, style inconsistencies, and missed edge cases. Read-only — does not edit files.
Agent Claude Code
Use when an EM needs to scan/triage across multiple repos, services, or large result sets in parallel — e.g. "which of these 5 repos reference this deprecated API", "find all TODOs related to X across the org's services". Read-only, keeps the dispatching session's context clean.
Skill Claude Code
Use when preparing notes for a 1:1 with a report, drafting written feedback, or summarizing a person's recent work/contributions ahead of a conversation or review cycle.
Skill Claude Code
Use when asked to generate or update architecture diagrams or ER (entity-relationship) diagrams from the codebase — the code is the source of truth, not existing docs.
Skill Claude Code
Use when the user asks how to reduce Claude Code costs, manage token usage, choose the right model for a task, or wants a review of whether a session/workflow is running efficiently.
Skill Claude Code
Use when the user asks for a standup update, daily summary, "what did I work on yesterday", or wants to recap recent commits before a team sync.
Skill Claude Code
Use when investigating a bug, test failure, or unexpected behavior and proposing a fix — always runs investigation in Plan Mode so no code changes happen until the root cause and approach are confirmed.
Skill Claude Code
Use when writing or reviewing code that crosses a trust boundary (user input, external APIs, file/network/DB I/O) — guards against invalid input, injection, unsafe failure modes, and missing validation at the edges without over-defending internal code.
Skill Claude Code
Use when reviewing local code changes for correctness and assessing the blast radius / impact of a change — what else could break, who/what depends on the changed code.
Skill Claude Code
Use when running the twice-daily project progress pulse — pulling Jira/Linear tasks and sending a Slack alert on key project movement (status changes, blockers, due-soon items).
Skill Claude Code
Use when generating or updating API documentation that follows the OpenAPI specification — daily sync that adds new endpoints to the catalog, notes key changes, and bumps the version.
Skill Claude Code
Use when the user wants to write or draft a pull request title and description, summarize a branch's changes for review, or prepare to open a PR.
Skill Claude Code
Use when asked to compare or analyze trade-offs between two or more technical solutions, approaches, libraries, or architectures — produces a structured comparison, not just a recommendation.
Skill Claude Code
Use when generating the weekly project progress summary (run Fridays) from Jira/Linear — covering what shipped, what's at risk, and what's coming next week.
Command Claude Code
Draft today's standup update from your recent git activity.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: