writing-plans
Create detailed implementation plans before coding (saves tokens later)
commit
This skill should be used when the user asks to commit changes, wants help writing commit messages, or has finished a task and needs to save their work. Triggers include: "commit this", "commit changes", "save my changes", "write a commit", "help me commit", "create a commit", "conventional commit", "/commit". Always confirms with user before committing. Never pushes to remote.
tool-discovery
Guide for discovering and using MCP tools via the discover_tools meta-tool. Use this skill when asked to perform tasks that require finding the right tools, when you see only discover_tools in your available tools, when asked "what tools are available", "find tools for X", or when planning multi-step workflows across JIRA, Slack, WhatsApp, or Google Docs.
remove-old-skills-from-workflow
Guide for removing skills from an existing workflow and updating all related documentation. Use when user wants to remove skills from a workflow (e.g., "remove skill", "delete skill", "移除技能", "删除技能").
github-pr-unresolved-review-fetcher
Fetch unresolved PR review comments from GitHub. Use when working with pull request reviews, addressing review feedback, or checking outstanding review comments on a PR. Triggers on requests like "get PR reviews", "fetch review comments", "show unresolved comments", or "what feedback is pending on this PR".
github-workflow-fixer
Analyze and fix GitHub Actions workflow failures. Use when workflows fail, CI/CD issues occur, or when debugging GitHub Actions runs. Triggers on requests like "fix workflow", "why did the build fail", "check CI status", "debug GitHub Actions", or "workflow failed".
graph-of-thoughts
INVOKE after research or brainstorming to synthesize findings. Produces visible aggregation with conflict resolution. Use when multiple inputs need combining into coherent output. Triggers: synthesizing research, combining ideas, merging approaches, integrating findings.
managing-adrs
Create and manage Architecture Decision Records (ADRs) with auto-numbering, template detection, and index maintenance. Use when user mentions "ADR", "architecture decision", "document this decision", "create ADR", editing ADR files (docs/adr/, doc/adr/, .adr/), or discussing architectural choices and tradeoffs.
interviewing
Systematic questioning to clarify requirements, goals, and constraints. Use when there's ambiguity about what the user wants, hidden complexity needs uncovering, or you need to understand before proceeding. Triggers on unclear requirements, vague goals, or when other skills encounter fundamental ambiguity.
brainstorm
This skill should be used when the user asks to "brainstorm", "design a feature", "think through an idea", "help me plan", or has a vague concept that needs refining into a technical specification through collaborative dialogue.
brainstorm
Collaborative brainstorming partner for multi-session ideation projects. Use when the user wants to brainstorm, ideate, explore ideas, or think through problems—whether for SaaS products, software tools, book ideas, newsletter content, business strategies, or any creative/analytical challenge. Handles session continuity across days/weeks via versioned markdown documents. Includes brainstorming methods catalog and supports both connected (cross-project awareness) and clean-slate modes.
log-to-project
Log work activity to a specific project folder. Maintains changelogs, session notes, and decision records for projects.
add-new-skills-to-workflow
Add new skills to an existing workflow and update all related documentation. Use when user wants to add skills from GitHub URLs to a workflow (e.g., "add this skill to the workflow", "为工作流添加技能"). Triggers on adding skills to workflows, updating workflow documentation after skill additions.
secondbrain-freshness
This skill should be used when the user asks for "freshness check", "freshness report", "what needs attention", "stale items", "review backlog", or mentions wanting to see what secondbrain content needs review or updating.
git-commit
Plans and executes git commits with optional TICKET_ID prefix. Analyzes staged changes, proposes optimal commit structure (single or multiple), generates descriptive messages with technical context, and executes after user approval. Use when committing code changes, creating atomic commits, or splitting large changesets.
unity-unitask
UniTask library expert specializing in allocation-free async/await patterns, coroutine migration, and Unity-optimized asynchronous programming. Masters UniTask performance optimizations, cancellation handling, and memory-efficient async operations. Use PROACTIVELY for UniTask implementation, async optimization, or coroutine replacement.
writing-plans
Use after brainstorming/design phase to create detailed implementation plans. Creates step-by-step plans clear enough for execution by any developer.
