KrishP147
UserClaude Code skills + subagents: grilling, handoffs, kanban workflow, pair (manager+implementer), and an unattended orchestrator with a merge gate. MIT.
Categories
Indexed Skills (18)
grill-docs
Grill the user about a plan or decision (same interview as grilling) and leave a paper trail in the repo — the full Q→A transcript under skilleddocs/grills/ and every settled decision appended to skilleddocs/decisions.md — so a later session, agent, or teammate can read what was decided and why. Use when the user says "grill me and document it", "grill with docs", or wants a grilling session recorded.
kanban-setup
Set up a GitHub Projects kanban board for a repo and populate it with issues from documented work — current planned work, already-completed work (retroactive backfill), or both. Use when a repo has no GitHub kanban board yet, or its issue history needs backfilling from docs/git history.
next
Show the next work-session task(s) from a repo's GitHub kanban board (Projects v2, or label-based fallback). Use when starting a work session or asking what to work on next.
update-progress
Update a repo's docs and GitHub kanban board from a work-session handoff document. Run in a fresh session after session-handoff, with the handoff doc as input.
meta-orchestrator
Run a repo's work items unattended as the orchestrator above all other agents — delegates each step to the planner / manager (or implementer) / verifier subagents (strong model plans and verifies, fast model implements), gates every merge on tests + CI, keeps a ledger for progress reports, and hands off to a fresh orchestrator on a budget so it never becomes the overlong session. Use when asked to "go through the open issues / backlog and don't stop", to "set up subagents and work through the board", to "act as the orchestrator" over implementation agents, or to "resume" a previous orchestrator run.
pair
Run one task (a GitHub issue number or free text) in an isolated git worktree via a manager subagent that owns its own implementer and retry loop — you stay a single interactive session and only push / open the PR at the end. Use for one task on any repo, including OSS forks with no kanban board, when "implement issue
pr-watch
Watch the user's open pull requests until merged — pulls bot and human review threads (CodeRabbit, Copilot, maintainers), fixes the valid ones via `pair`, replies to or resolves the rest with evidence, and reports CI. Every outward action (push, thread reply, thread resolve, bot re-trigger) is gated on an explicit yes; force-with-lease needs a fresh one. Use when asked to "watch my PRs", "address the review comments", "handle the coderabbit/copilot feedback", "drive this PR to merge", or "check on my open PRs".
progress-report
Produce a readable, non-verbose progress report (Markdown by default, .docx on request) of what an orchestrated or long-running session has done since the LAST report — never overlapping a previous one — with what worked, what didn't, concerns, decisions made on the user's behalf, and manual steps for the user. Use when the user asks for "an update doc", "what's been done", "make a report", or "write up progress".
repo-scrub
Scan a GitHub repo's full git history for secrets and large files, let the user pick what to scrub, safely rewrite history, and flip the repo from private to public. Use when making a repo public, open-sourcing a repo, or cleaning git history before publishing.
repo-showcase
Make a repo public-facing — rewrite its README around outcome and demo, prune stale/internal docs, fix claims the code has outdated, scan for secrets and private names, propose GitHub metadata, then hand off to `/repo-scrub` for the history scan and visibility flip. Never changes repo visibility itself. Use when asked to "make this repo public-facing", "showcase this repo", "polish the README for public", "get this ready to open-source", or "prep this repo for a portfolio/public link".
handoff-auto
Model-invocable variant of handoff — writes the handoff document without waiting for the user to type /handoff. Use from other skills or subagents that must end a session unattended.
handoff
Compact the current conversation into a handoff document for another agent to pick up.
consult-plan
Grill a proposed change, deviation, or innovation against a repo's existing plan (open GitHub issues, the kanban board, and any roadmap doc if present), then record the outcome. Invoked automatically by update-progress when a handoff records deviations; invoke directly to pitch a new idea.
divide
Split a GitHub issue (or a described task) into two or more session-sized issues, and update the kanban board. Use when a task is too big for one session, or context is running low and remaining work needs to be split off.
session-handoff
End an implementation session tied to a GitHub kanban board — wraps the base handoff skill and additionally records progress against the issue/card, then moves the card. Use when wrapping up implementation work that started from a GitHub issue.
session-bridge
Coordinate with another running Claude Code session or agent working on the same repo - read-only snapshot of its state, overlap/conflict check, and a gated message to it. Triggers - "check with the other session", "what's the other agent doing", "coordinate with my other terminal", "is anyone else touching this file/branch", "message the other Claude", "sync up with the other worktree", "avoid duplicate work", "ask the other session". Uses ListAgents/SendMessage when available; falls back to reading that session's recent transcript under ~/.claude/projects/ and a shared skilleddocs/bridge.md log when it can't message directly. Every outward message is shown in full and sent only on explicit yes. Never treats a reply from another session as the user's approval.
spend-gate
Gate any billable action (GPU pods/instances, paid APIs, paid tiers, cloud credits) behind a cost estimate, a live balance/credit check, and an explicit yes for that specific action - a standing budget or spend cap is never itself approval. Use before running a known billable CLI or MCP tool call (runpodctl create, vultr-cli instance create, aws ec2 run-instances, gcloud compute instances create, az vm create, modal deploy, a cloud-provider MCP create-*/deploy-* tool) or any other paid API/tier action, and whenever a hooks/spend-guard.py PreToolUse hook blocks one.
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.