- Skills
- 182
- 仓库
- 2
- 职业覆盖
- 1
- 场景覆盖
- 3
- Stars
- ★ 3
David Huu Pham 的 Skills 182
afk-implement
Run an unattended ("AFK") implementation session as the supervisor — scope small progressive iterations, push feature branches, open pull requests, drive review waves to clean, and never merge. Use when the user says they are going AFK or to bed, asks for overnight autonomous implementation, says "don't block on me", "open PRs but don't merge", "progressive adoption", or "stack changes".
protocol
Aura protocol reference documentation — 12-phase workflow, agent roles, constraints, and coding standards. Read when you need to understand the full workflow or look up conventions.
protocol
暂无简介
example
暂无简介
example
暂无简介
example
暂无简介
write-go-tests
Use when adding or extending Go tests in strike-cli — *_test.go, table-driven cases, fixtures, httptest, tool Ask helpers, TUI harnesses, coverage gaps. Do not use for running tests only (use test-and-validate).
tui-components
Use when building or restyling strike's TUI — views, panels, modals, pickers, badges, dashboards, status rows, or any layout work in internal/tui. Covers the internal/tui/ui component catalog and internal/tui/theme tokens. Do not use for backend/engine work (internal/engine, internal/provider, internal/tool, internal/permission, internal/session, internal/auth, internal/host) — those packages have no UI surface.
tmux-capture-driver
Drive an interactive terminal program (Claude Code, Codex, OpenCode, or any TUI) from an agent through tmux, step by step, and prove each step by an observable artefact. Carries the send-keys rules that were measured to work, the trust-prompt sequences per program, turn-completion detection, bounded condition waits, non-interactive fallbacks, and the failure modes seen in practice. Use when an agent must operate a TUI it cannot attach to, obtain files or output that only an interactive session produces, or hand a partly driven tmux session to another agent.
test-and-validate
Use when running tests, validation, CI checks, coverage, race detection, vet, build, or verifying strike-cli changes. Trigger on make test, go test, lint, verify, validate, regression, or before claiming work done.
smoke
Offline product happy-path checks for strike-cli — boot, echo turn, interrupt, session resume. Use when verifying user-visible CLI/TUI/session/auth changes, before release, or when issue-handler tier B/C touches cmd/, engine, tui input/keymap, session, or auth.
run-harness-capture
Run a live capture sitting that records raw lifecycle-hook payloads from real Claude Code, Codex and OpenCode sessions through pasture's capture sink, so the bytes can be cleared into fixtures. Carries the kit rules (a binary and transports generated with the version roots moved), the three environment variables, the dry run, per-harness setup and trigger recipes with expected file names, the fault line that is expected, the report format for the clearance step, and the safety rules (live sessions only, never the live store, nothing committed before clearance, nothing pushed before the user's ACCEPT). Use when a pin bump or a coverage slice needs authentic host payloads, or when the user says to run the captures.
release
Cut a strike-cli GitHub release from main — preflight, notes, annotated tag, watch release.yml, verify assets. Use when shipping a version (v0.x.y), tagging, or preparing release notes.
pasture-usage
Use when operating the Pasture task tracker from the command line — creating, reading, updating, and closing tasks; labels; dependencies; comments and timelines; agent/author attribution; and store/namespace selection. Covers the required --author flag, exit codes, and the gotchas we have hit in practice (write-lock contention, shell quoting, URI capture, two-dash vs slash IDs).
pasture-performance
Use when a pasture read, replay, hook or query is slow, or before claiming a speedup. Covers the session replay path, query plans, benchmarks, invariants, and the evidence a speedup needs.
issue-orchestrator
Drive open GitHub issues on strike-cli to merge via parallel worktrees — parse wave/depends/blocks/conflicts headers, dispatch issue-handler agents, prefer bugs-first, never parallelize conflicting issues. Use when asked to orchestrate issues, farm the backlog, run the issue board, or coordinate multiple agents on GitHub issues.
issue-handler
Own a GitHub issue end-to-end in strike-cli — worktree, implement, test, PR, spawn review agents that comment on the PR, address feedback in a loop, CI, merge. Use when asked to handle/fix/close an issue, ship a PR from an issue, or babysit issue work through merge to main.
issue-create-and-handle
Turn a reported problem or requested change into a refined GitHub issue, obtain explicit approval, create and assign the issue to the authenticated GitHub user, then immediately hand it to issue-handler. Use when asked to file an issue and start work on it, create-and-handle an issue, or turn a bug report into an assigned implementation workflow.