Loading...
Loading...
Found 84 Skills
Comprehensive verification with parallel test agents. Use when verifying implementations or validating changes.
Design exploration with parallel agents. Use when brainstorming ideas, exploring solutions, or comparing alternatives.
Conduct web research and material downloading for each node. Read node-list.txt, launch multiple sub-agents to perform parallel web research on node content, deeply retrieve relevant webpages/articles/blogs/literature, download and save them locally, and output a download.txt file to record the material sources for each node. Suitable for document writing scenarios that require extensive background information, data verification, and reference sources.
Manage background coding agents in tmux sessions. Spawn Claude Code or other agents, check progress, get results.
Comprehensive Elixir/Phoenix code review with optional parallel agents
Show status of all features in .dev/. Scans feature folders using parallel agents, generates a status report, and offers to archive completed features.
Comprehensive iOS/SwiftUI code review with optional parallel agents
Plan a non-trivial code change end-to-end — size triage (XS–XL), slicing strategy, optional parallel subagent dispatch, per-slice Implement → Test → Verify → Commit discipline. Use for any multi-file change, refactor across files, executing a planned task from any planning source, cross-cutting modification (analytics sweep / i18n / library migration), or when about to write more than ~100 lines. 也用于增量实现 / 切片落地 / 推进已规划任务 / 跨切面改动。Skip only for trivial XS edits and pure documentation / configuration changes.
Use to review uncommitted changes and recent commits in the working tree. Dispatches 8 specialized review agents in parallel and returns a consolidated report
Execute plan files by launching multiple parallel subagents to complete tasks simultaneously. Triggers on explicit "/parallel-task" commands.
Find dead code using parallel subagent analysis and optional CLI tools, treating code only referenced from tests as dead. Use when the user asks to "find dead code", "find unused code", "find unused exports", "find unreferenced functions", "clean up dead code", or "what code is unused". Analysis-only — does not modify or delete code.
Review changed code for reuse opportunities, quality issues, and inefficiencies using three parallel review agents, then fix any issues found. Triggers when the user says "simplify", "clean up the code", "review the changes", or after run-plan execution when code quality verification is needed.