Skip to main content
Run any Skill in Manus
with one click
dinhanhthi
GitHub creator profile

dinhanhthi

Repository-level view of 48 collected skills across 1 GitHub repositories.

skills collected
48
repositories
1
updated
2026-07-06
repository explorer

Repositories and representative skills

cf-review
software-quality-assurance-analysts-and-testers

Dispatch code review to a subagent. Use when the user wants code reviewed — e.g. "review this", "review my changes", "check the code", "look over this", "code review", "any issues with this?", "is this code ok?", "review before merge", "review the diff", "what do you think of these changes?". Also triggers on requests to review specific files, commits, or branches.

2026-07-06
cf-review
software-quality-assurance-analysts-and-testers

Dispatch code review to a subagent. Use when the user wants code reviewed — e.g. "review this", "review my changes", "check the code", "look over this", "code review", "any issues with this?", "is this code ok?", "review before merge", "review the diff", "what do you think of these changes?". Also triggers on requests to review specific files, commits, or branches.

2026-07-06
cf-checkpoint
software-developers

Save a concise checkpoint of the current conversation's context — goal, decisions, breaking changes, next steps — into a file for resuming later in a DIFFERENT conversation. Use when the user says things like "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (condenses context within the SAME conversation), this produces a durable, resumable snapshot for a fresh conversation. Unlike $cf-remember (durable project-wide facts/conventions for AI recall across all future work), this is a transient per-conversation resume artifact. Does NOT auto-invoke — slash-only.

2026-07-05
cf-plan
software-developers

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", "I want to create", "create for me", "build for me", "add feature", "implement", "make a", "set up", "I need a", "can you build", "help me build", "how should we implement", "design a solution", "architect", "scaffold", "plan out", "figure out how to", "what's the best way to build". Also triggers on task descriptions that imply multi-step implementation work requiring upfront planning.

2026-07-05
cf-research
software-developers

In-depth research on a topic with web search and structured output. Use when the user wants deep research before building — e.g. "research this", "look into this library", "investigate how X works", "compare these options", "what are the best practices for", "deep dive into", "study this technology", "analyze this repo", "explore the ecosystem around". Also triggers when the user needs to understand a technology, library, or architecture pattern in depth before making decisions.

2026-07-05
cf-checkpoint
software-developers

Save a concise checkpoint of the current conversation's context — goal, decisions, breaking changes, next steps — into a file for resuming later in a DIFFERENT conversation. Use when the user says things like "save a checkpoint", "checkpoint this conversation", "capture context", "snapshot the conversation", "cf-checkpoint". Unlike /compact (condenses context within the SAME conversation), this produces a durable, resumable snapshot for a fresh conversation. Unlike /cf-remember (durable project-wide facts/conventions for AI recall across all future work), this is a transient per-conversation resume artifact. Does NOT auto-invoke — slash-only.

2026-07-05
cf-plan
software-developers

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", "I want to create", "create for me", "build for me", "add feature", "implement", "make a", "set up", "I need a", "can you build", "help me build", "how should we implement", "design a solution", "architect", "scaffold", "plan out", "figure out how to", "what's the best way to build". Also triggers on task descriptions that imply multi-step implementation work requiring upfront planning.

2026-07-05
cf-research
software-developers

In-depth research on a topic with web search and structured output. Use when the user wants deep research before building — e.g. "research this", "look into this library", "investigate how X works", "compare these options", "what are the best practices for", "deep dive into", "study this technology", "analyze this repo", "explore the ecosystem around". Also triggers when the user needs to understand a technology, library, or architecture pattern in depth before making decisions.

2026-07-05
Showing top 8 of 48 collected skills in this repository.
Showing 1 of 1 repositories
All repositories loaded