将一次执行的改动/命令/验证/产物整理成结构化 `manifest_<topic>.json`，并落盘到 `<MM_DD>/codex/artifact/`，用于证据链与可追溯交付。适用于“写manifest/记录证据链/把今天做了什么落成json/生成artifact清单”等请求。
Research WoW addon development topics using CLI tools, Blizzard UI source, and documentation. Covers API discovery, pattern research, and Ace3 usage. Use when investigating unfamiliar APIs, finding Blizzard patterns, or learning. Triggers: research, find, search, API, Blizzard UI, documentation, Ace3.
typeof操作符返回一个字符串，表示未经计算的操作数的类型；该运算符数据类型（返回字符串，对应列表如图）
Build slide decks and presentations for research talks. Use this for making PowerPoint slides, conference presentations, seminar talks, research presentations, thesis defense slides, or any scientific talk. Provides slide structure, design templates, timing guidance, and visual validation. Works with PowerPoint and LaTeX Beamer.
基于当天的 Intake 文件生成可执行计划 `plan_<topic>.md`，并落盘到 `<MM_DD>/codex/plan/`；计划包含 Tasks+DoD+Dependencies、可选 Gates、Deliverables（当天目录路径）与 Rollback。适用于“基于intake写计划/生成plan_<topic>.md/补DoD和门禁”等请求。
批量推进编排 Skill：把“一堆事项/bug/想法/审稿意见”收口为 Assumptions → Triage Queue → Sprint Plan（含并行组/DoD/Gates/回滚）→ Next Backlog；可选将结果落盘到 `<MM_DD>/codex/intake/intake_<topic>.md`、`<MM_DD>/codex/plan/plan_<topic>.md`（以及 `<MM_DD>/codex/exec/exec_<topic>.md`）。适用于“我有一堆事想批量推进/做个冲刺计划/把 backlog 变成可执行任务”等请求。
Contribute skills back to upstream via branch and PR
Skill（SKILL.md）の保守・更新・新規作成を対話で行い、整合性と検証手順を維持したまま反映する。Skill更新、skill update、Skillメンテナンス、Skill追加を依頼されたときに使用する。
Use when you need to work with Docker Compose. This skill provides Docker Compose file generation with comprehensive guidance and automation. Trigger with phrases like "generate docker-compose", "create compose file", or "configure multi-container app".
Analyzes git commit history and generates professional changelogs with semantic versioning, conventional commit support, and multiple output formats (Keep a Changelog, Conventional, GitHub). Use when editing CHANGELOG.md, CHANGELOG.txt, or HISTORY.md files, preparing release notes, creating releases, bumping versions, updating changelog, documenting changes, writing release notes, tracking changes, version bump, tag release, or when user mentions "changelog", "release notes", "version history", "release", "semantic versioning", or "conventional commits".
Generates interactive 3D HTML visualization of the session-local occupancy grid. Opens in browser.
Deletes merged git branches (local and remote) and flags stale unmerged branches for manual review. Use when user mentions "cleanup branches", "delete merged branches", "prune old branches", "remove stale branches", "branch cleanup", or runs /cleanup-branches command.
Creates GitHub Pull Requests with existing PR detection, branch pushing, and intelligent title/body generation. Use when user requests to create pull request, open PR, update PR, push for review, ready for review, send for review, get this reviewed, make a PR, share code, request review, create draft PR, submit for review, run /create-pr command, or mentions "PR", "pull request", "merge request", "code review", "GitHub PR", or "draft".
Use the docmgr CLI to manage ticketed docs (create tickets, add docs, relate code files with file-note, update changelog, and search). Use when the user asks how to use docmgr, wants a docmgr command sequence, or needs docmgr best practices (file-note, quoting, doctor).
Lists local and remote git branches that are candidates for cleanup — merged but not deleted, and inactive branches with no commits in a configurable period (default 3 months). Use when user mentions "stale branches", "old branches", "branch cleanup", "prune branches", "dead branches", "unused branches", "inactive branches", "branch hygiene", or asks to "list branches to delete", "find stale branches", or runs /stale-branches command.
validate_skills.pyを実行してSkills/Agents/Commandsの構文を検証し、エラーを修正してログを記録する。「バリデーション」「構文検証」「Skillsチェック」を依頼されたときに使用する。
Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.
Verify Spring Boot 4.x projects for correct dependencies, configuration, and migration readiness. Use when analyzing pom.xml, build.gradle, application.yml, discussing Spring Boot project setup, dependency versions, configuration validation, version compatibility, migration to Spring Boot 4, deprecated dependencies, or when user mentions "verify project", "check dependencies", "upgrade Spring Boot", "migration readiness", "Jackson 3", "@MockBean deprecated", or "Spring Security 7".
Spring Boot 4 REST API implementation patterns. Use when creating REST controllers, request validation, exception handlers with ProblemDetail (RFC 9457), API versioning, content negotiation, or WebFlux reactive endpoints. Covers @RestController patterns, Bean Validation 3.1, global error handling, and Jackson 3 configuration.
Spring Boot 4 testing strategies and patterns. Use when writing unit tests, slice tests (@WebMvcTest, @DataJpaTest), integration tests, Testcontainers with @ServiceConnection, security testing (@WithMockUser, JWT), or Modulith event testing with Scenario API. Covers the critical @MockitoBean migration from @MockBean.