schovi

@schovi source repo

17 skills
0 followers
1 week ago last updated

▌
Jira Auto Detector · schovi
Auto-detection: when user mentions Jira issues (PROJ-123, ABC-456, XY-789, 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 PROJ-123'), passive listings, technical identifiers (endpoint names), already-fetched issues, or casual references.

0 installs
▌
Framework Doctor · schovi bundle
Validate an initialized workflow repo and keep its shipped files and task metadata current. Use when the user says "/workflow:framework-doctor", "check the board", "validate work tracking", or when another workflow skill hits an inconsistent structure. Reports findings first; refreshes drifted files only after the user approves. Not a migrator — for a repo with no board use /workflow:framework-init.

0 installs
▌
Gh Pr Auto Detector · schovi
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.

0 installs
▌
Datadog Auto Detector · schovi
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.

0 installs
▌
Debug · schovi
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 ticket key, GitHub issue/PR, observability or any other source URL, error description, or stack trace file. Returns problem summary, root cause, fix proposal, testing strategy, and rollout plan.

0 installs
▌
Review · schovi
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, a tracker ticket, any source URL, a branch, or local files.

0 installs
▌
Work · schovi
Implement one selected task from an initialized workflow board with a minimal deliberate loop: read routed docs, plan, implement, validate, and commit. Use when the user explicitly invokes "/workflow:work", "/work", "/work 051", or "use $work". When workflow/AGENTS.md exists, also use for an unmistakable request to implement the next, numbered, or Ready workflow-board task. Do not use for generic implementation requests. If explicitly invoked in an uninitialized repo, stop and suggest /workflow:framework-init; never invoke it automatically.

0 installs
▌
Delegate · schovi bundle
Delegate a self-contained task to a Codex (GPT-5.6) subagent through the bundled codex-delegate.sh wrapper, which hides the event stream and returns only the final message plus a resumable session id. Use when the user says "/codex:delegate", "ask codex", "delegate this to codex", or when offloading token-heavy but well-specified work (bulk implementation, mechanical migrations, standalone investigation or review, throwaway research) would preserve Claude context for judgment work. Skip for anything finishable in a handful of tool calls, or tasks whose context can't be written into one self-contained prompt.

0 installs
▌
Address · schovi
Drive an open GitHub PR to green: fetch it, triage every unresolved review comment (fix it, decline it with evidence-backed reasoning when it's a false positive or low-value nit, or defer it to a human when it needs a decision) and diagnose every failing CI job, then (after you approve, or automatically with --auto) implement, push, reply to each thread with what changed or why not, and resolve the ones you addressed. Use when the user says "/schovi:address", "address the PR comments", "resolve the review comments", "fix the failing CI and respond", "handle the review feedback on #123", or points at a PR and asks to work through its open feedback. Previews the plan and waits for confirmation before changing code, unless --auto is given. Uses /schovi:publish to commit, push, and rewrite the PR description for the behaviour that changed.

0 installs
▌
Publish · schovi
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. Takes the change's source from a ticket key, a GitHub reference, any source URL, a local spec file or folder, plain text, or the commit history. Auto-commits uncommitted changes first.

0 installs
▌
Groom · schovi
Refine tasks in the repo's workflow/ status folders into implementable specs, and capture concrete work items found during exploration onto that board. Use when the user explicitly invokes "/workflow:groom", "/groom", "groom 052", or "use $groom". In an initialized repo (workflow/AGENTS.md exists), also use without being asked when an exploration, investigation, audit, or review — by you or by an agent reporting back — has produced concrete work items the user wants tracked, and for an unmistakable request to put an ask onto that board. Do not use for generic planning or task-refinement requests, and do not use in a repo that has no workflow/AGENTS.md. If explicitly invoked in an uninitialized repo, stop and suggest /workflow:framework-init; never invoke it automatically.

0 installs
▌
Feedback · schovi
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.

0 installs
▌
Status · schovi
Show a decision-oriented overview of tracked workflow-board work in the current repo, or a one-line-per-repo table with "all". Always use when the user explicitly invokes "/workflow:status" or "use $status", including when that invocation carries a follow-up question (scoped to a tag, which tasks can run in parallel, what a chain waits on) — the question is the request, not a reason to skip the skill. When workflow/AGENTS.md exists in this initialized repo, also use for an unmistakable question about that board's queue, progress, dependencies, or gates. Do not use for generic project-status questions unrelated to that board. Read-only; never edits, moves, commits, or initializes the framework.

0 installs
▌
Release · schovi
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).

0 installs
▌
Decision · schovi
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.

0 installs
▌
Batch Work · schovi bundle
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.

0 installs
▌
Framework Init · schovi bundle
Explicit invocation only. Initialize the workflow framework in a repo that does not 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 only when the user explicitly invokes "/workflow:framework-init", says "init the workflow" or "set up the board here", or invokes "use $framework-init". Never invoke this skill because a different workflow skill found no workflow/AGENTS.md. A repo with an existing legacy markdown board must be migrated to status folders by hand first.

0 installs

17 published skills