claude-schovi

Refine a task in the repo's workflow/ status folders into an implementable spec. Use when the user says "/workflow:groom", "/groom", "groom 052", "refine this task", or hands a fuzzy ask that should enter the board. Requires an initialized framework (workflow/AGENTS.md exists); otherwise route to /workflow:framework-init first.

Implement one task from the repo's workflow/ status folders, or any small ad-hoc ask, with a minimal deliberate loop: read routed docs, brief plan, implement, validate, atomic completion commit. Use when the user says "/workflow:work", "/work", "/work 051", asks for the next task, or hands an implementation task. Requires an initialized framework (workflow/AGENTS.md exists); otherwise route to /workflow:framework-init first.

Run multiple Ready tasks from the repo's workflow/ status folders sequentially in isolated subagents, with a consolidated report. Use when the user asks to batch-run tasks, run work overnight, run the first N Ready tasks, or invokes /workflow:batch-work, /batch-work, or /batch.

Append a decision record with a stable D<N> handle to the repo's decision log. Use when the user says "/workflow:decision", "log this decision", "record why we chose X", or when /workflow:work surfaces an A/B/X choice a future agent might plausibly flip. Skip for choices that die with the task.

Validate a repo's workflow framework and migrate legacy layouts. Use when the user says "/workflow:framework-check", "check the board", "validate work tracking", "migrate to the workflow plugin", or when another workflow skill hits an inconsistent or legacy structure. Reports findings and a migration plan first; applies fixes only after the user approves.

Initialize the workflow framework in a repo that doesn't have one: create the workflow/ status folders, install the board-view script, write the repo contract, scaffold the docs skeleton, and route AGENTS.md to the plugin. Use when the user says "/workflow:framework-init", "init the workflow", "set up the board here", or when another workflow skill finds no workflow/AGENTS.md. For repos with an existing legacy board (docs/board.md or a workflow/board.md file), use /workflow:framework-check instead — it migrates.

Show a combined work-status view across every repo that has workflow/ status folders. Use when the user says "/workflow:status", "board status", "what's in progress across my projects", or asks for a cross-repo overview of tracked work. Read-only; never edits or commits.

Auto-detection: when user mentions Datadog resources (app.datadoghq.com URLs, 'error rate of service X', 'check logs for Y', monitor/incident/service-health questions) and needs data, automatically fetches condensed summary via datadog-analyzer subagent. Skips auto-fetch for past tense mentions, already-fetched data, informational discussions, or vague references.

Deep root cause analysis with fix proposal. Use when the user says "/schovi:debug", "debug this issue", "find the root cause", or "investigate this bug", with a Jira ID, GitHub issue/PR, Datadog URL, error description, or stack trace file. Returns problem summary, root cause, fix proposal, testing strategy, and rollout plan.

Auto-detection: when user mentions GitHub PRs (URLs, #123, owner/repo#123, 'PR #123') and needs context (asking questions, checking CI status, comparing, applying changes), automatically fetches condensed PR summary via gh-pr-reviewer subagent. Skips auto-fetch for past tense mentions, passive listings, technical identifiers, or already-fetched PRs.

Auto-detection: when user mentions Jira issues (EC-1234, IS-8046, PROJ-567, Atlassian URLs) and needs context (asking about issue, requesting implementation, analyzing, comparing), automatically fetches condensed summary via jira-analyzer subagent. Skips auto-fetch for past tense mentions ('I fixed EC-1234'), passive listings, technical identifiers (endpoint names), already-fetched issues, or casual references.

Create GitHub pull request with smart description generation. Use when the user says "/schovi:publish", asks to "create a PR", "publish", "open a pull request", or wants to push and create/update a GitHub PR. Auto-commits uncommitted changes first.

Post feedback to a GitHub PR in either direction: as a reviewer (inline + general comments, optional Approve / Comment / Request-changes verdict), or as the author replying to change-request threads with what you changed. Use when the user says "/schovi:feedback", asks to "post these comments to the PR", "send this review back", "reply to the review threads", or "I made the requested changes, respond on the PR" — usually after /schovi:review or after pushing fixes. Always previews and waits for confirmation before posting; it replies to threads but never resolves them. With no PR link, writes the comments as text output instead.

Cut a CI-gated GitHub release for projects distributed through Homebrew, GoReleaser, GitHub Releases, casks, formulae, or SemVer tags. Handles version selection, CI gating, release notes, optional GoReleaser automation, tag publishing, release verification, and a follow-up documentation-sync pull request. Explicit invocation only (/homebrew:release in Claude Code, `use $release` in Codex).

Structured code review with risk, security, and performance assessment. Use when the user says "/schovi:review", "review this PR", "review #123", "code review", or asks for a review of a GitHub PR, Jira ticket, branch, or local files.