Answer questions about Coding Friend — skills, agents, hooks, CLI, config, memory, hosts, parameters. Auto-invoke for CF capabilities or how to use a skill — e.g. "what skills are available?", "how does coding friend work?", "list all skills", "how do I use cf-plan?", "what is cf-tdd?", "is the CLI required?". Do NOT…
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 knowledge for human learning from conversation. Auto-invoke on substantial new technical knowledge, debugging breakthroughs, architecture decisions, or complex explanations. Do NOT auto-invoke for trivial edits, typo fixes, or routine operations. Unlike /cf-remember (AI recall), this is educational notes for…
Structured optimization — baseline, analyze, optimize, measure, compare. Auto-invoke for performance/speed — e.g. "this is slow", "make it faster", "optimize", "performance", "bottleneck", "too many queries", "high latency", "memory leak", "speed up", "timeout", "N+1". Do NOT auto-invoke for minor refactors or style…
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. Use when the user wants to plan, build, create, or implement something — e.g. "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". Also triggers on multi-step work…
Extract project knowledge to docs/memory for AI recall. Triggers: "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention". Auto-invoke: non-obvious bug fix → bugs/; architecture decision → decisions/; new convention →…
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 code review to a subagent. Triggers: "review this", "review my changes", "check the code", "code review", "any issues with this?", "review before merge", "review the diff". Also for 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.
Use when writing new production code, adding features, implementing, or refactoring — e.g. "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "write a test", "add tests", "create a component", "implement the API", "add a route". Also…
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.
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.