Loading...
Loading...
Found 58 Skills
Semantic code search using mgrep for efficient codebase exploration. This skill should be used when searching or exploring codebases with more than 30 non-gitignored files and/or nested directory structures. It provides natural language semantic search that complements traditional grep/ripgrep for finding features, understanding intent, and exploring unfamiliar code.
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
Deep codebase exploration. Triggers: research, explore, investigate, understand, deep dive, current state.
一个全面、结构化的特性开发工作流程，包含代码库探索、架构设计、质量审查和实现等专门阶段。在构建需要以下条件的新特性时使用：（1）在做出更改之前了解现有代码库，（2）通过系统性的提问澄清模糊的需求，（3）在实现之前设计周到的架构，（4）通过多维度的代码审查确保质量。非常适合涉及多个文件、需要架构决策、包含复杂集成或需求有些不明确的功能特性。
Use when exploring unfamiliar codebases, before searching for code, or after editing files. Builds a structural AST index (classes, functions, imports, call graph) from 12 languages via tree-sitter. Trigger: /graphify
Create a design brief through an interactive interview, codebase exploration, and experience design decisions. Saved as a markdown file in the project. Use when user wants to write a design brief, plan a new feature or page, define a UI direction, or mentions "brief".
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
Specialized feature development agents. Use for deep codebase exploration and architecture design during feature development.
Write BDD test scenarios in Gherkin for a feature
Pre-indexed code knowledge graph (MCP, SQLite + tree-sitter) for faster, lower-token exploration of brownfield codebases. Use when starting work on a repo larger than ~500 files or when the task involves cross-file traversal — "where is X used", "what calls Y", "what breaks if I change Z", "trace flow from A to B", "explain this subsystem". Skip for single-file edits or sessions shorter than the cold-start cost. Triggers include "codegraph", "code graph", "index this repo", "where is X defined", "find callers of", "callees of", "blast radius of changing X", "explore this codebase". Replaces grep + Read loops with O(1) SQLite lookups and FTS5 search via 8 MCP tools.
Use when discovering codebase facts, context, patterns, constraints, or unknowns through focused, incremental, read-only investigation without diagnosing a failure or modifying state.
AI-Native Issue-Driven development workflow. From GitHub Issue to merged PR: parse issue, explore codebase, design technical plan, execute with agent team, create PR, and cleanup. Use when a user wants to implement a GitHub Issue end-to-end: `/issue-flow #123` or `/issue-flow` to pick from open issues.