Work through deferred side-tasks in docs/later/. Triggers: "do the later tasks", "process docs/later", "work through the backlog", "what did we defer", "resolve deferred items", "cf-later-do". Routes to /cf-fix or /cf-plan; removes the file only after verified-done. Slash-only — NOT auto-invoked. Does NOT capture new…
Extract educational notes for the human from the conversation (unlike /cf-remember, which stores project memory for AI recall). TRIGGER — substantial new technical knowledge, a debugging breakthrough, an architecture decision explained, or a complex explanation worth keeping; the user says "explain what we learned"…
Structured performance work — baseline, analyze, optimize, measure, compare. TRIGGER — "this is slow", "make it faster", "optimize", "performance", "bottleneck", "too many queries", "high latency", "memory leak", "speed up", "timeout", "N+1", or any request to reduce time, memory, or query count with numbers to prove…
Resume an existing /cf-plan from where execution last stopped. Triggers: "resume the plan", "continue the plan", "pick up where we left off", "finish the plan", "resume ". Requires a plan under docs/plans/. Does NOT create new plans (use /cf-plan).
Brainstorm and write an implementation plan before coding. TRIGGER — the user wants to plan, build, create, or implement something: "let's build", "let's create", "add feature", "implement", "set up", "design a solution", "architect", "scaffold", "plan out", "what's the best way to build"; any multi-step or multi-file…
Save project knowledge to docs/memory for AI recall (unlike /cf-learn, which writes educational notes for the human). TRIGGER — "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention"; after a non-obvious bug fix → bugs/, an…
In-depth research with web search and structured output. Triggers: "research this", "look into this library", "investigate how X works", "compare these options", "best practices for", "deep dive into", "study this technology".
Collect and act on an external AI review. Reads the result file, presents findings, offers to fix. Triggers: "review in", "collect review", "check review results", "cf-review-in", "import review".
Generate a review prompt for an external AI (Gemini, Codex, ChatGPT, or a human). Triggers: "get a second opinion", "external review", "review out", "send for review", "cf-review-out", "prepare review for gemini".
Dispatch a multi-agent code review of the current changes and report Critical / Important / Suggestions / Summary. TRIGGER — "review this", "review my changes", "check the code", "code review", "any issues with this?", "review before merge", "review the diff"; reviewing specific files, commits, or branches…
Scan the project and populate memory (architecture, conventions, stack, features). Triggers: "scan the project", "scan the codebase", "bootstrap memory", "populate memory", "analyze the project". Token-heavy — always warn before proceeding.
Continue or resume Google Antigravity conversations with the native session controls. Use when the user asks to resume, continue, or restore an Antigravity session. Antigravity owns its transcript format, so Coding Friend does not copy or rewrite session files.
Verify, commit, push, and create a PR. Triggers: "ship it", "push and create PR", "let's ship", "create a PR", "open a pull request", "ready to merge". Supports --dry-run.
Gate before writing production code — direct implementation by default, TDD (RED→GREEN→REFACTOR) with --add-tests or config tdd: true. TRIGGER — any new feature, implementation, or refactor: "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this"…
Personal teacher — after a task, explains what happened as a conversational narrative (approach, alternatives, tradeoffs, pitfalls, lessons). Unlike /cf-learn (structured notes), this is a deep-dive so the human understands what happened and why.
Completion gate — demands fresh verification evidence (test run, command output, manual check) before any claim that work is done. TRIGGER — about to say "done", "complete", "fixed", "passing", "ready to commit" or "ready to ship", or to summarize finished work; the end of any cf-tdd, cf-fix, cf-plan, or cf-optimize…
Catch up after absence — summarize git history for a user. Triggers: "warm up", "catch me up", "what happened while I was away", "summarize recent changes", "what changed since I left".
Runs before the agent uses a tool for Read, Write, Edit, Glob, Grep and apply_patch tool calls, executing privacy-block.sh and scout-block.cjs (2 commands). From dinhanhthi/coding-friend.
★not rated 4 yesterdayA
tokens not measured
originalMIT
Runs when a subagent starts, executing agent-tracker.sh. From dinhanhthi/coding-friend.
★not rated 4 yesterdayA
tokens not measured
originalMIT
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: