tyabu12
UserA shareable kit of Claude Code assets — skills, agents, hooks, and rules.
Categories
Indexed Skills (6)
dispatch
Fan out multiple independent tasks in the current repo to worktree-isolated implementer subagents running in parallel. Each task: implement → auto-detected verification (just/make/gradle/swift/npm/composer/cargo/pytest/dotnet) → commit → push → draft PR (assigned + labeled) → critic review of the diff. One approval gate on the dispatch plan; issue-backed tasks get self-assigned and labeled in-progress. Use when the user has a batch of small-to-medium independent, well-specified tasks (backlog items, issue numbers, cleanup lists) to run in parallel. For a single large feature that needs planning and design judgment, use /orchestrate instead.
orchestrate
Project-agnostic feature orchestration — plan → issue → worktree → implement → review → PR, driven by a per-project profile. A project's own `orchestrate` skill shadows this one (project scope wins over global).
promote-memories
Triage per-user memory — promote durable entries into a rules file (global ~/.claude/rules/ or a project's .claude/rules/) AND retire (delete/trim) SHIPPED trackers — select candidates, classify, draft at concept level, self-check, and hand off to the project's PR workflow for any promotion.
skill-retro
Monthly evidence-driven retrospective of this kit's skills. Gathers evidence — friction logs from ~/.claude/skill-feedback/, skill-invocation traces from session transcripts, outcome data from dispatch-created PRs, and official-docs drift — then proposes SKILL.md fixes ONLY where evidence exists, delivered as a draft PR to the claude-kit repo. No evidence → no change. Reviews itself too (dogfooding). Designed to run monthly, manually or as a scheduled routine, via /skill-retro.
work-log
Extract and format a work log from conversation history under ~/.claude/projects/. Argument is the number of days to look back (default 7).
write-adr
Draft a new Architecture Decision Record into the repo's ADR directory (new files only — not for amending an existing ADR). Use when asked to write an ADR, record an architecture decision, or document a design trade-off.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.