all publishers

dinhanhthi

@dinhanhthi source repo

120 published skills · page 1 of 2

  1. ▌
    Cf Plan Resume 4 · dinhanhthi
    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 <slug>". Requires a plan under docs/plans/. Does NOT create new plans (use /cf-plan).
    4 repo stars
  2. ▌
    Cf Plan Review 4 · dinhanhthi bundle
    Review a saved /cf-plan folder with a fresh reviewer before implementing; triggers "review the plan", "plan review", "second opinion on the plan", "check the plan before implementing", "cf-plan-review"; --fix/--inline (or config planReviewFix) applies Critical/Important findings without asking and re-reviews until clean, --no-fix forces off; does NOT review code (use /cf-review).
    4 repo stars
  3. ▌
    Cf Verification 4 · dinhanhthi
    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 run; the user asks "is it done?" or "does it work?". SKIP — mid-task progress notes, exploratory or read-only answers, and plans that have not been implemented yet.
    4 repo stars
  4. ▌
    Cf Showcase 4 · dinhanhthi bundle
    Make an intro video (mp4) and/or a poster (png/pdf/html) for the current project, built from the repo's real features, names and brand, and saved to docs/showcase/ with a re-renderable source/ folder. Use --video, --poster, or both. Use this whenever the user wants marketing or launch material for their own project, even if they don't say "showcase". Triggers: "make an intro video", "promo video for this project", "demo video", "launch video", "poster for this project", "make a banner for the README", "showcase this project".
    4 repo stars
  5. ▌
    Cf Checkpoint From 4 · dinhanhthi
    Load a saved checkpoint as working context, then do the next ask. Triggers: "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "restore conversation context". First word is the slug; `--recap` prints a summary. Does NOT create checkpoints (use /cf-checkpoint).
    4 repo stars
  6. ▌
    Cf Review 4 · dinhanhthi bundle
    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; automatically after cf-plan, cf-fix, and cf-optimize complete. SKIP — reviewing a plan document (use /cf-plan-review), quick questions about how code works (use /cf-ask), and formatting-only changes. --fix applies Critical/Important findings, --commit also commits (config: review.fix, review.commit).
    4 repo stars
  7. ▌
    Cf Session 4 · dinhanhthi
    Continue or resume Devin CLI conversations with the native session controls. Use when the user asks to resume, continue, or restore a Devin session. Devin owns its transcript format, so Coding Friend does not copy or rewrite session files.
    4 repo stars
  8. ▌
    Cf Showcase 2 · dinhanhthi bundle
    Make an intro video (mp4) and/or a poster (png/pdf/html) for the current project, built from the repo's real features, names and brand, and saved to docs/showcase/ with a re-renderable source/ folder. Use --video, --poster, or both. Use this whenever the user wants marketing or launch material for their own project, even if they don't say "showcase". Triggers: "make an intro video", "promo video for this project", "demo video", "launch video", "poster for this project", "make a banner for the README", "showcase this project".
    4 repo stars
  9. ▌
    Cf Later Do 4 · dinhanhthi
    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 items (that is /cf-later or capture-later.sh).
    4 repo stars
  10. ▌
    Cf Optimize 4 · dinhanhthi
    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 it. SKIP — minor refactors, readability or style changes, and correctness bugs that are not performance-related (use cf-fix).
    4 repo stars
  11. ▌
    Cf Remember 4 · dinhanhthi
    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 architecture decision → decisions/, a new convention → conventions/, a feature flow or gotcha → features/. SKIP — trivial fixes, simple config changes, or educational exchanges (use /cf-learn).
    4 repo stars
  12. ▌
    Cf Research 4 · dinhanhthi bundle
    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".
    4 repo stars
  13. ▌
    Cf Showcase 3 · dinhanhthi bundle
    Make an intro video (mp4) and/or a poster (png/pdf/html) for the current project, built from the repo's real features, names and brand, and saved to docs/showcase/ with a re-renderable source/ folder. Use --video, --poster, or both. Use this whenever the user wants marketing or launch material for their own project, even if they don't say "showcase". Triggers: "make an intro video", "promo video for this project", "demo video", "launch video", "poster for this project", "make a banner for the README", "showcase this project".
    4 repo stars
  14. ▌
    Cf Review In 4 · dinhanhthi
    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".
    4 repo stars
  15. ▌
    Cf Sys Debug 4 · dinhanhthi
    Systematic 4-phase debugging — root cause, hypothesis testing, regression-guarded fix, mandatory bug doc. TRIGGER — non-trivial or recurring bugs: "still broken", "same error again", "came back", flaky/intermittent/race, "used to work, now broken", hard-to-reproduce, works locally but fails in CI, "find the root cause", "investigate", "diagnose", "why is this happening"; prefer over cf-fix once a fix has already failed. SKIP — trivial typos, one-line fixes, obvious config errors, or first-time simple bugs (use cf-fix).
    4 repo stars
  16. ▌
    Cf Checkpoint 4 · dinhanhthi
    Save a conversation checkpoint (goal, decisions, breaking changes, next steps) for a DIFFERENT conversation. Triggers: "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (same chat) or /cf-remember (project facts). Slash-only — does NOT auto-invoke.
    4 repo stars
  17. ▌
    Cf Review Out 4 · dinhanhthi bundle
    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".
    4 repo stars
  18. ▌
    Cf Later 4 · dinhanhthi
    Defer a side-task to docs/later/ without loading it into the main conversation. Usage: /cf-later <self-contained description>. On Claude Code runs in a forked subagent and returns one line. Slash-only — NOT auto-invoked. Resolve items later with /cf-later-do.
    4 repo stars
  19. ▌
    Cf Showcase · dinhanhthi bundle
    Make an intro video (mp4) and/or a poster (png/pdf/html) for the current project, built from the repo's real features, names and brand, and saved to docs/showcase/ with a re-renderable source/ folder. Use --video, --poster, or both. Use this whenever the user wants marketing or launch material for their own project, even if they don't say "showcase". Triggers: "make an intro video", "promo video for this project", "demo video", "launch video", "poster for this project", "make a banner for the README", "showcase this project".
    4 repo stars
  20. ▌
    Cf Ask 4 · dinhanhthi bundle
    Quick Q&A about the codebase → docs/memory. Use for focused project questions — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "why is this done this way?". Unlike /cf-research, one answer.
    4 repo stars
  21. ▌
    Cf Fix 4 · dinhanhthi
    Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted stack trace or error message. SKIP — new features (use cf-plan or cf-tdd), performance complaints (use cf-optimize), and recurring or hard-to-reproduce bugs after a failed fix (use cf-sys-debug).
    4 repo stars
  22. ▌
    Cf Tdd 4 · dinhanhthi bundle
    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", "write a test", "add tests", "create a component", "implement the API", "add a route"; also when planning shifts into writing code — load this first. SKIP — docs-only changes, config edits, non-code files, or questions with no requested change.
    4 repo stars
  23. ▌
    Cf Help 4 · dinhanhthi bundle
    Answer questions about Coding Friend itself — skills, agents, hooks, CLI, config, memory, hosts, parameters. TRIGGER — "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?", or any question about a cf-* name, flag, hook, or config key. SKIP — general coding questions unrelated to Coding Friend, and requests to run a skill (invoke that skill instead).
    4 repo stars
  24. ▌
    Cf Plan 4 · dinhanhthi bundle
    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 work that needs sequencing. SKIP — a single obvious edit, a reported bug (use cf-fix), deciding whether to build at all (use /cf-advise), or resuming an existing plan (use /cf-plan-resume).
    4 repo stars
  25. ▌
    Cf Scan 4 · dinhanhthi bundle
    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.
    4 repo stars
  26. ▌
    Cf Ship 4 · dinhanhthi
    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.
    4 repo stars
  27. ▌
    Cf Warm 4 · dinhanhthi
    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".
    4 repo stars
  28. ▌
    Cf Later 2 · dinhanhthi
    Defer a side-task to docs/later/ without loading it into the main conversation. Usage: $cf-later <self-contained description>. On Claude Code runs in a forked subagent and returns one line. Slash-only — NOT auto-invoked. Resolve items later with $cf-later-do.
    4 repo stars
  29. ▌
    Cf Later 3 · dinhanhthi
    Defer a side-task to docs/later/ without loading it into the main conversation. Usage: /cf-later <self-contained description>. On Claude Code runs in a forked subagent and returns one line. Slash-only — NOT auto-invoked. Resolve items later with /cf-later-do.
    4 repo stars
  30. ▌
    Cf Learn 4 · dinhanhthi bundle
    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", "make notes on this", "cf-learn". SKIP — trivial edits, typo fixes, routine operations, or knowledge that belongs in project memory rather than learning notes (use /cf-remember).
    4 repo stars
  31. ▌
    Cf Teach 4 · dinhanhthi
    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.
    4 repo stars
  32. ▌
    Cf Advise 4 · dinhanhthi
    Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike /cf-plan (builds) or /cf-ask (looks up code), this only advises.
    4 repo stars
  33. ▌
    Cf Commit 4 · dinhanhthi bundle
    Smart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
    4 repo stars
  34. ▌
    Cf Design 4 · dinhanhthi bundle
    UI design workflow — scan patterns, design new UI, or modify UI consistently. Use to redesign a component/page, change colors/typography/style, or extract the design system. Triggers: "make it look like", "update the styling", "redesign this", "match the existing style", "add a dark mode", "make it more minimal".
    4 repo stars
  35. ▌
    Cf Later · dinhanhthi
    Defer a side-task to docs/later/ without loading it into the main conversation. Usage: /cf-later <self-contained description>. On Claude Code runs in a forked subagent and returns one line. Slash-only — NOT auto-invoked. Resolve items later with /cf-later-do.
    4 repo stars
  36. ▌
    Cf Ask 2 · dinhanhthi bundle
    Quick Q&A about the codebase → docs/memory. Use for focused project questions — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "why is this done this way?". Unlike $cf-research, one answer.
    4 repo stars
  37. ▌
    Cf Fix 2 · dinhanhthi
    Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted stack trace or error message. SKIP — new features (use cf-plan or cf-tdd), performance complaints (use cf-optimize), and recurring or hard-to-reproduce bugs after a failed fix (use cf-sys-debug).
    4 repo stars
  38. ▌
    Cf Tdd 2 · dinhanhthi bundle
    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", "write a test", "add tests", "create a component", "implement the API", "add a route"; also when planning shifts into writing code — load this first. SKIP — docs-only changes, config edits, non-code files, or questions with no requested change.
    4 repo stars
  39. ▌
    Cf Help 2 · dinhanhthi bundle
    Answer questions about Coding Friend itself — skills, agents, hooks, CLI, config, memory, hosts, parameters. TRIGGER — "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?", or any question about a cf-* name, flag, hook, or config key. SKIP — general coding questions unrelated to Coding Friend, and requests to run a skill (invoke that skill instead).
    4 repo stars
  40. ▌
    Cf Plan 2 · dinhanhthi bundle
    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 work that needs sequencing. SKIP — a single obvious edit, a reported bug (use cf-fix), deciding whether to build at all (use $cf-advise), or resuming an existing plan (use $cf-plan-resume).
    4 repo stars
  41. ▌
    Cf Scan 2 · dinhanhthi bundle
    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.
    4 repo stars
  42. ▌
    Cf Ship 2 · dinhanhthi
    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.
    4 repo stars
  43. ▌
    Cf Warm 2 · dinhanhthi
    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".
    4 repo stars
  44. ▌
    Cf Learn 2 · dinhanhthi bundle
    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", "make notes on this", "cf-learn". SKIP — trivial edits, typo fixes, routine operations, or knowledge that belongs in project memory rather than learning notes (use $cf-remember).
    4 repo stars
  45. ▌
    Cf Teach 2 · dinhanhthi
    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.
    4 repo stars
  46. ▌
    Cf Advise 2 · dinhanhthi
    Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike $cf-plan (builds) or $cf-ask (looks up code), this only advises.
    4 repo stars
  47. ▌
    Cf Commit 2 · dinhanhthi bundle
    Smart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
    4 repo stars
  48. ▌
    Cf Design 2 · dinhanhthi bundle
    UI design workflow — scan patterns, design new UI, or modify UI consistently. Use to redesign a component/page, change colors/typography/style, or extract the design system. Triggers: "make it look like", "update the styling", "redesign this", "match the existing style", "add a dark mode", "make it more minimal".
    4 repo stars
  49. ▌
    Cf Review 2 · dinhanhthi bundle
    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; automatically after cf-plan, cf-fix, and cf-optimize complete. SKIP — reviewing a plan document (use $cf-plan-review), quick questions about how code works (use $cf-ask), and formatting-only changes.
    4 repo stars
  50. ▌
    Cf Session 2 · dinhanhthi
    Continue or branch Codex conversations with the native session controls. Use when the user asks to resume, continue, fork, or restore a Codex session. Codex owns its transcript format, so Coding Friend does not copy or rewrite session JSONL files.
    4 repo stars
  51. ▌
    Cf Later Do 2 · dinhanhthi
    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 items (that is capture-later.sh).
    4 repo stars
  52. ▌
    Cf Optimize 2 · dinhanhthi
    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 it. SKIP — minor refactors, readability or style changes, and correctness bugs that are not performance-related (use cf-fix).
    4 repo stars
  53. ▌
    Cf Remember 2 · dinhanhthi
    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 architecture decision → decisions/, a new convention → conventions/, a feature flow or gotcha → features/. SKIP — trivial fixes, simple config changes, or educational exchanges (use $cf-learn).
    4 repo stars
  54. ▌
    Cf Research 2 · dinhanhthi bundle
    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".
    4 repo stars
  55. ▌
    Cf Ask 3 · dinhanhthi bundle
    Quick Q&A about the codebase → docs/memory. Use for focused project questions — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "why is this done this way?". Unlike /cf-research, one answer.
    4 repo stars
  56. ▌
    Cf Fix 3 · dinhanhthi
    Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted stack trace or error message. SKIP — new features (use cf-plan or cf-tdd), performance complaints (use cf-optimize), and recurring or hard-to-reproduce bugs after a failed fix (use cf-sys-debug).
    4 repo stars
  57. ▌
    Cf Tdd 3 · dinhanhthi bundle
    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", "write a test", "add tests", "create a component", "implement the API", "add a route"; also when planning shifts into writing code — load this first. SKIP — docs-only changes, config edits, non-code files, or questions with no requested change.
    4 repo stars
  58. ▌
    Cf Review In 2 · dinhanhthi
    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".
    4 repo stars
  59. ▌
    Cf Sys Debug 2 · dinhanhthi
    Systematic 4-phase debugging — root cause, hypothesis testing, regression-guarded fix, mandatory bug doc. TRIGGER — non-trivial or recurring bugs: "still broken", "same error again", "came back", flaky/intermittent/race, "used to work, now broken", hard-to-reproduce, works locally but fails in CI, "find the root cause", "investigate", "diagnose", "why is this happening"; prefer over cf-fix once a fix has already failed. SKIP — trivial typos, one-line fixes, obvious config errors, or first-time simple bugs (use cf-fix).
    4 repo stars
  60. ▌
    Cf Help 3 · dinhanhthi bundle
    Answer questions about Coding Friend itself — skills, agents, hooks, CLI, config, memory, hosts, parameters. TRIGGER — "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?", or any question about a cf-* name, flag, hook, or config key. SKIP — general coding questions unrelated to Coding Friend, and requests to run a skill (invoke that skill instead).
    4 repo stars
  61. ▌
    Cf Plan 3 · dinhanhthi bundle
    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 work that needs sequencing. SKIP — a single obvious edit, a reported bug (use cf-fix), deciding whether to build at all (use /cf-advise), or resuming an existing plan (use /cf-plan-resume).
    4 repo stars
  62. ▌
    Cf Scan 3 · dinhanhthi bundle
    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.
    4 repo stars
  63. ▌
    Cf Ship 3 · dinhanhthi
    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.
    4 repo stars
  64. ▌
    Cf Warm 3 · dinhanhthi
    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".
    4 repo stars
  65. ▌
    Cf Checkpoint 2 · dinhanhthi
    Save a conversation checkpoint (goal, decisions, breaking changes, next steps) for a DIFFERENT conversation. Triggers: "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (same chat) or $cf-remember (project facts). Slash-only — does NOT auto-invoke.
    4 repo stars
  66. ▌
    Cf Review Out 2 · dinhanhthi bundle
    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".
    4 repo stars
  67. ▌
    Cf Learn 3 · dinhanhthi bundle
    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", "make notes on this", "cf-learn". SKIP — trivial edits, typo fixes, routine operations, or knowledge that belongs in project memory rather than learning notes (use /cf-remember).
    4 repo stars
  68. ▌
    Cf Teach 3 · dinhanhthi
    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.
    4 repo stars
  69. ▌
    Cf Plan Resume 2 · dinhanhthi
    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 <slug>". Requires a plan under docs/plans/. Does NOT create new plans (use $cf-plan).
    4 repo stars
  70. ▌
    Cf Plan Review 2 · dinhanhthi bundle
    Review a saved $cf-plan folder with a fresh reviewer before implementing; triggers "review the plan", "plan review", "second opinion on the plan", "check the plan before implementing", "cf-plan-review"; does NOT review code (use $cf-review).
    4 repo stars
  71. ▌
    Cf Advise 3 · dinhanhthi
    Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike /cf-plan (builds) or /cf-ask (looks up code), this only advises.
    4 repo stars
  72. ▌
    Cf Commit 3 · dinhanhthi bundle
    Smart conventional commit with diff analysis. Triggers: "commit this", "commit my changes", "save my work", "create a commit", "git commit", "stage and commit".
    4 repo stars
  73. ▌
    Cf Design 3 · dinhanhthi bundle
    UI design workflow — scan patterns, design new UI, or modify UI consistently. Use to redesign a component/page, change colors/typography/style, or extract the design system. Triggers: "make it look like", "update the styling", "redesign this", "match the existing style", "add a dark mode", "make it more minimal".
    4 repo stars
  74. ▌
    Cf Review 3 · dinhanhthi bundle
    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; automatically after cf-plan, cf-fix, and cf-optimize complete. SKIP — reviewing a plan document (use /cf-plan-review), quick questions about how code works (use /cf-ask), and formatting-only changes.
    4 repo stars
  75. ▌
    Cf Verification 2 · dinhanhthi
    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 run; the user asks "is it done?" or "does it work?". SKIP — mid-task progress notes, exploratory or read-only answers, and plans that have not been implemented yet.
    4 repo stars
  76. ▌
    Cf Session 3 · dinhanhthi
    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.
    4 repo stars
  77. ▌
    Cf Later Do 3 · dinhanhthi
    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 items (that is capture-later.sh).
    4 repo stars
  78. ▌
    Cf Optimize 3 · dinhanhthi
    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 it. SKIP — minor refactors, readability or style changes, and correctness bugs that are not performance-related (use cf-fix).
    4 repo stars
  79. ▌
    Cf Remember 3 · dinhanhthi
    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 architecture decision → decisions/, a new convention → conventions/, a feature flow or gotcha → features/. SKIP — trivial fixes, simple config changes, or educational exchanges (use /cf-learn).
    4 repo stars
  80. ▌
    Cf Research 3 · dinhanhthi bundle
    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".
    4 repo stars
  81. ▌
    Cf Review In 3 · dinhanhthi
    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".
    4 repo stars
  82. ▌
    Cf Sys Debug 3 · dinhanhthi
    Systematic 4-phase debugging — root cause, hypothesis testing, regression-guarded fix, mandatory bug doc. TRIGGER — non-trivial or recurring bugs: "still broken", "same error again", "came back", flaky/intermittent/race, "used to work, now broken", hard-to-reproduce, works locally but fails in CI, "find the root cause", "investigate", "diagnose", "why is this happening"; prefer over cf-fix once a fix has already failed. SKIP — trivial typos, one-line fixes, obvious config errors, or first-time simple bugs (use cf-fix).
    4 repo stars
  83. ▌
    Cf Checkpoint From 2 · dinhanhthi
    Load a saved checkpoint as working context, then do the next ask. Triggers: "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "restore conversation context". First word is the slug; `--recap` prints a summary. Does NOT create checkpoints (use $cf-checkpoint).
    4 repo stars
  84. ▌
    Cf Checkpoint 3 · dinhanhthi
    Save a conversation checkpoint (goal, decisions, breaking changes, next steps) for a DIFFERENT conversation. Triggers: "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (same chat) or /cf-remember (project facts). Slash-only — does NOT auto-invoke.
    4 repo stars
  85. ▌
    Cf Review Out 3 · dinhanhthi bundle
    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".
    4 repo stars
  86. ▌
    Cf Plan Resume 3 · dinhanhthi
    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 <slug>". Requires a plan under docs/plans/. Does NOT create new plans (use /cf-plan).
    4 repo stars
  87. ▌
    Cf Plan Review 3 · dinhanhthi bundle
    Review a saved /cf-plan folder with a fresh reviewer before implementing; triggers "review the plan", "plan review", "second opinion on the plan", "check the plan before implementing", "cf-plan-review"; does NOT review code (use /cf-review).
    4 repo stars
  88. ▌
    Cf Verification 3 · dinhanhthi
    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 run; the user asks "is it done?" or "does it work?". SKIP — mid-task progress notes, exploratory or read-only answers, and plans that have not been implemented yet.
    4 repo stars
  89. ▌
    Cf Checkpoint From 3 · dinhanhthi
    Load a saved checkpoint as working context, then do the next ask. Triggers: "resume from checkpoint", "load checkpoint", "continue from checkpoint", "cf-checkpoint-from", "restore conversation context". First word is the slug; `--recap` prints a summary. Does NOT create checkpoints (use /cf-checkpoint).
    4 repo stars
  90. ▌
    Cf Ask · dinhanhthi bundle
    Quick Q&A about the codebase → docs/memory. Use for focused project questions — e.g. "how does X work?", "where is Y defined?", "what's the flow for Z?", "explain this module", "why is this done this way?". Unlike /cf-research, one answer.
    4 repo stars
  91. ▌
    Cf Fix · dinhanhthi
    Quick bug-fix workflow — reproduce, find the root cause, fix via cf-implementer, verify, auto-review. TRIGGER — the user reports a bug or broken behavior: "fix this", "it's broken", "not working", "there's a bug", "this crashes", "debug this", "it throws", "failing test", "regression", "unexpected behavior"; a pasted stack trace or error message. SKIP — new features (use cf-plan or cf-tdd), performance complaints (use cf-optimize), and recurring or hard-to-reproduce bugs after a failed fix (use cf-sys-debug).
    4 repo stars
  92. ▌
    Cf Tdd · dinhanhthi bundle
    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", "write a test", "add tests", "create a component", "implement the API", "add a route"; also when planning shifts into writing code — load this first. SKIP — docs-only changes, config edits, non-code files, or questions with no requested change.
    4 repo stars
  93. ▌
    Cf Help · dinhanhthi bundle
    Answer questions about Coding Friend itself — skills, agents, hooks, CLI, config, memory, hosts, parameters. TRIGGER — "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?", or any question about a cf-* name, flag, hook, or config key. SKIP — general coding questions unrelated to Coding Friend, and requests to run a skill (invoke that skill instead).
    4 repo stars
  94. ▌
    Cf Plan · dinhanhthi bundle
    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 work that needs sequencing. SKIP — a single obvious edit, a reported bug (use cf-fix), deciding whether to build at all (use /cf-advise), or resuming an existing plan (use /cf-plan-resume).
    4 repo stars
  95. ▌
    Cf Scan · dinhanhthi bundle
    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.
    4 repo stars
  96. ▌
    Cf Ship · dinhanhthi
    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.
    4 repo stars
  97. ▌
    Cf Warm · dinhanhthi
    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".
    4 repo stars
  98. ▌
    Cf Learn · dinhanhthi bundle
    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", "make notes on this", "cf-learn". SKIP — trivial edits, typo fixes, routine operations, or knowledge that belongs in project memory rather than learning notes (use /cf-remember).
    4 repo stars
  99. ▌
    Cf Teach · dinhanhthi
    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.
    4 repo stars
  100. ▌
    Cf Advise · dinhanhthi
    Decision advisory via structured interview — never writes code or plans. Use when the user wants help DECIDING — e.g. "should I", "is X worth it", "which approach", "help me decide between A and B", "am I overthinking this", "what would you recommend", "pros and cons of". Unlike /cf-plan (builds) or /cf-ask (looks up code), this only advises.
    4 repo stars