Skip to main content
Manusで任意のスキルを実行
ワンクリックで
dinhanhthi
GitHub クリエイタープロフィール

dinhanhthi

1 件の GitHub リポジトリにある 48 件の収集済み skills をリポジトリ単位で表示します。

収集済み skills
48
リポジトリ
1
更新
2026-07-06
リポジトリエクスプローラー

リポジトリと代表的な skills

cf-review
ソフトウェア品質保証アナリスト・テスター

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
ソフトウェア品質保証アナリスト・テスター

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
ソフトウェア開発者

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
ソフトウェア開発者

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
ソフトウェア開発者

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
ソフトウェア開発者

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
ソフトウェア開発者

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
ソフトウェア開発者

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
このリポジトリの収集済み skills 48 件中、上位 8 件を表示しています。
1 件中 1 件のリポジトリを表示
すべてのリポジトリを表示しました