Describe what this skill does, when it should be used, and what kind of tasks should trigger it.
Describe what this skill does, when it should be used, and what kind of tasks should trigger it.
npx skills add https://github.com/Wynne-cwb/skills --skill my-skillこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
| name | my-skill |
| description | Describe what this skill does, when it should be used, and what kind of tasks should trigger it. |
Use this skill when the task matches the description above.
references/: detailed docs or domain notes loaded only when neededscripts/: deterministic helpers for repetitive workassets/: output assets or templates that should not be loaded into context by defaultFind real sent email records from Automizely/AfterShip message logs and extract or preview the HTML content that was actually sent. Use when a user asks to locate a sent email, inspect email delivery/message records, compare candidate emails, preview email HTML, or get the HTML source from a real outbound email record.
Guide Claude Code to act as Team Lead for an existing GSD milestone after the user has already created the milestone. Use when the user asks Claude Code to take over a GSD milestone, act as Team Lead, use TeamCreate, create TeamMates, run autonomous milestone execution, batch all gsd-discuss-phase decisions first, auto-research plan phases, execute phases without repeated user intervention, or defer UAT/manual acceptance testing until milestone completion. Explicitly treat TeamCreate as the required Claude Code mechanism for creating fresh TeamMates, with each TeamMate executing exactly one bounded GSD step; do not confuse TeamCreate with generic subagents or non-TeamCreate mechanisms. 仅适用于用户希望 Claude Code 作为项目 Team Lead 接管 GSD Milestone、先集中完成 Discuss Phase 人工决策、后续通过 TeamCreate 新建 TeamMate，每个 TeamMate 只执行一个边界清晰的 GSD step，并在 Milestone 完成后统一收口 UAT 测试和修复。
Safe GitHub pull request workflow for feature branches, target environment branches, forks, and AfterShip upstream repositories. Use whenever the user asks Codex to 提 PR, 创建 PR, 开 PR, 发 PR, submit a PR, open a PR, create a PR, raise a PR, publish a PR, ship a branch, or prepare a GitHub pull request from a feature branch such as feat/feature-name into a target branch such as testing, testing/*, release/*, release-incy, or release-pear. Handles multi-repo PR work, infers target_branch from the current branch upstream tracking branch when omitted, conflict checks, fork-vs-upstream push rules, target-branch conflict resolution, PR title formatting with CI/JIRA/Gitmoji, and PR body verification notes.
Inspect and fix self-hosted SonarQube pull request failures. Use when the user asks to read, summarize, debug, or fix Sonar/SonarQube PR issues, Quality Gate failures, failed Sonar bot comments, New Bugs, New Vulnerabilities, New Code Smells, coverage or duplication gate failures, especially for AfterShip Sonar at sonar.aftership.org where SONAR_TOKEN may need to be created and stored in shell startup files.
Use when diagnosing unexpected behavior, failed workflows, bugs, browser or Node.js runtime issues, logs, traces, or when preparing a root-cause hypothesis. 诊断异常、定位 bug、判断修复方向时使用：先建立证据表，区分运行时事实和代码推断，避免多层猜测；证据不足时添加 copy-friendly 浏览器日志或本地 Node.js JSONL 日志。
Use before get-shit-done implementation to turn rough product ideas into a reviewed PRD under prds/*. Stops after PRD approval; does not create specs, implementation plans, code, or invoke implementation skills.