Menu
Use when the user says "bug:", "feature:", "feat:", "fix:", "issue:", "chore:", or explicitly "/issue". File a GitHub issue without interrupting the current workflow. Run as a background Task so the main conversation continues unblocked.
Use when the user says "delegate", "assign bot work", "dispatch issues", "triage open issues", "send to bot", or explicitly "/delegate". Scans open GitHub issues, classifies which are bot-delegatable, enriches them with design direction and context, and assigns via @claude comments. Analyzes prior bot failures and decomposes large issues.
Use when the user says "crystallize", "compact", "compile", "distill", or asks to reduce a skill's reliance on LLM prose reasoning. Phase-transitions deterministic operations out of skill docs into real scripts with real test data. Rewrites the SKILL.md to be shorter and call the scripts instead of describing the logic. Aggressive about the boundary: LLM does judgment, prose, ambiguity resolution. Scripts do math, time comparison, parsing, counting, aggregation, schema validation.
This skill should be used when the user asks to "test on device", "test on emulator", "run emulator", "launch AVD", "test PWA", "test on Android", "test on mobile", "verify on real device", "check on phone", or discusses testing a feature on an actual device or emulator rather than headless Playwright. Also use when validating features that headless browsers cannot cover (biometric, PWA install, Chrome autofill, touch gestures, password managers). Use proactively when a feature has been implemented that touches any of these capabilities.
Protocol for capturing a complete development arc (TRACE). Includes telemetry, strategy pivots, logs, and performance metadata. Use this to record the "how and why" of an objective, especially for performance-critical or non-deterministic tasks.
Use when the user says "cycle", "pump", "sdlc", "next cycle", or "/cycle". Runs one full SDLC cycle — discover, prioritize, cluster, delegate, develop, gate — filtered by theme.
Use when the user says "develop", "work on issue", "implement issue", "fix issue N", or explicitly "/develop N". Spawns a local develop agent in a worktree to implement one or more GitHub issues. Supports batch mode ("/develop 3,9,16") with max 4 parallel agents. Without arguments, auto-proposes bot-labeled issues ranked by risk and relevance.
| name | issue |
| description | Use when the user says "bug:", "feature:", "feat:", "fix:", "issue:", "chore:", or explicitly "/issue". File a GitHub issue without interrupting the current workflow. Run as a background Task so the main conversation continues unblocked. |
Process reference:
.claude/process.mddefines the label taxonomy, workflow states, and conventions that this skill must follow.
File a GitHub issue from an in-conversation observation. The user types something like
bug: default WSS URL is missing /ssh and expects it handled without derailing current work.
Spawn a general-purpose agent with the prompt from .claude/agents/issue-manager.md.
Use model: "sonnet", run_in_background: true. Custom subagent_types are broken in
file-based discovery (see .claude/rules/agents.md).
Background agents auto-deny permissions not pre-approved in settings.json. If the
agent fails on permissions, run it in foreground instead or file directly in the main
conversation.
Extract from the user's message. Apply exactly one Type label per .claude/process.md:
| Prefix | Type label | Title prefix |
|---|---|---|
| bug: | bug | bug: |
| fix: | bug | fix: |
| feature: | feature | feature: |
| feat: | feature | feat: |
| chore: | chore | chore: |
| issue: | (classify from description) | (classify from description) |
If the prefix is issue: or /issue, read the description and pick the best type label.
Add Domain labels if the description matches keywords:
| Keywords | Label |
|---|---|
| touch, gesture, swipe, pinch, scroll | touch |
| ios, safari, webkit, iphone, ipad | ios |
| security, vault, credential, encrypt | security |
| ux, ui, layout, mobile, keyboard, panel | ux |
| image, sixel, kitty, iterm | image |
Add Shape labels when applicable:
| Condition | Label |
|---|---|
| Issue needs research before code can be written | spike |
| Issue needs emulator/device validation | device |
| Issue is too large for one bot pass | composite |
Do NOT apply delegation labels (bot, divergence) -- those are managed by /delegate
and /integrate respectively.
Build a concise issue body. No filler.
scripts/gh-ops.sh version
Code: abc1234 | Server: 0.1.0:def5678 (or server not running).
If they differ, flag it as (STALE -- server hasn't been restarted).Check for recent test artifacts in either test results directory. If the report JSON
was modified within 30 minutes (stat -c %Y vs date +%s), include relevant evidence:
Appium tests (primary):
Legacy CDP emulator tests:
Both paths:
4. Per-test screenshots: check test-results/*-android-emulator/ for relevant PNGs
If a recording exists but no frames have been extracted (no frames/ directory or it's
empty), run scripts/review-recording.sh to generate uniform frame samples. This
is useful when the issue relates to visual behavior that screenshots alone don't capture.
Only include artifacts clearly connected to the issue. If nothing is recent or relevant, skip this section entirely.
If the issue is actionable (bug with clear reproduction, feature with clear scope), append:
@claude <Specific instruction for what to investigate or implement.
Reference relevant files, test commands, or prior issues.>
Do NOT add @claude for research issues (spike), things needing real-device validation
(device), or vague requests that need scoping. The /delegate skill handles enriching
issues with full delegation context and applying the bot label -- this step is just a
lightweight hint for obviously bot-ready issues.
Before filing, check for existing issues:
scripts/gh-ops.sh search "<key phrase from title>"
If a match exists, warn the user and ask whether to file or comment on the existing one.
Write the body to a temp file, then file using the wrapper script. Body template:
Filed while working on <context> (<branch>).
<Problem statement or feature description with technical details.>
## Reproduction
<Steps to reproduce, or user need for features.>
## Version
<output from `scripts/gh-ops.sh version`>
<If mismatched: "(STALE -- server hasn't been restarted)">
## Test Evidence
<Only if recent artifacts exist (Step 3). Otherwise omit this section entirely.>
- Run: <pass/fail summary from report.json>
- Failed: <test names and error snippets>
- Frames: <relevant filenames from frames/ or review/>
- Recording: test-results/emulator/recording.mp4 (<timestamp>)
@claude <Specific bot instructions, if actionable (Step 4).>
Write the composed body to a temp file, then file:
# Write body to temp file (use the Write tool, not a heredoc)
# Then file:
scripts/gh-file-issue.sh --title "<prefix>: <title>" --label "<type>" --label "<domain>" --body-file /tmp/issue-body.md
Important: Use the Write tool to create /tmp/issue-body.md, then call the script.
Do NOT use heredocs or $(cat <<EOF) in the bash command -- that's what causes
per-command approval prompts. One Write + one scripts/gh-file-issue.sh call.
Only include --label flags for labels that apply. Type is always one. Domain and shape
are zero or more. See .claude/process.md for the full label taxonomy.
Output: Filed: <issue-url>
If filing failed, report the error. Do not retry silently.
bug:) -- ask for at least a one-phrase descriptiongh not authenticated -- report error immediately.claude/process.md -- all are pre-created on the repo