Loading...
Loading...
Found 2,037 Skills
View a plan's tasks and progress, regardless of output format.
通过分析提交历史、分类更改并将技术提交转换为清晰的、面向客户的发布说明，自动从 git 提交创建面向用户的更新日志。将数小时的手动更新日志编写工作缩短为几分钟的自动生成。
Review the current session for errors, issues, snags, and hard-won knowledge, then update the rules/ files (or AGENTS.md if no suitable rule file exists) with actionable learnings.
Creates a new numbered issue document in docs/issue/ following the project's standard issue format, and simultaneously creates the corresponding Korean translation in docs/dev/issue/. Use this whenever starting new work — features, bug fixes, tasks, or investigations. The user may say "create an issue", "new issue", "이슈 만들어줘", or simply describe work they want to start.
Summarize work done in a spec/plan document.
Design software architectures with appropriate patterns for scale, maintainability, and team structure. Covers layered, hexagonal, event-driven, CQRS, and modular monolith architectures. Produces architecture decision records, component diagrams, and dependency maps. Prevents over-engineering, premature distribution, and architectural drift.
Load project context from .claude/ directory at the start of every task. This ensures Gemini CLI has the same coding rules, design decisions, and library constraints as Claude Code.
Plain text formatting that's readable raw AND rendered
Document creative decisions and protocol evolution in structured chronicle format.
Manage template overrides for customizing Kata output formats. List available templates, copy defaults for local editing, edit overrides, validate template schemas. Triggers include "customize template", "override template", "edit template", "template overrides", "list templates", "show templates", "template customization", "manage templates", "what templates can I customize", "template schema", "custonmize Kata", "custom config".
Manual QA testing — verify features end-to-end as a user would, using every tool available (browser, macOS, bash, APIs). Focuses on what formal test suites cannot capture: visual correctness, UX flows, usability judgment, integration reality, edge cases, and failure modes. Standalone or composable with /ship. Triggers: qa, qa test, manual test, test the feature, verify it works, exploratory testing, smoke test, end-to-end verification.
Writes structured blameless postmortems for production incidents. Use when an incident has occurred and you need to document what happened, the impact, root cause, timeline, and action items without blaming individuals.