krish

Plugin krish from marketplace krish in KrishP147/skills. Commands read from the repo's manifest — 23 days ago.

Skills (29)

• find-me-a-skill

  Suggest which skill or workflow fits a task, with model and /effort per step and paste-ready commands; runs nothing. Use for "which skill should I use", "find me a skill", "how should I run this", "what model/effort for this".

• gap-scan

  Survey one or more repos (code, commits, docs, tests, issues) and return a ranked, evidence-cited list of gaps, bugs, and extension ideas as issue-ready items. Read-only apart from its report. Use for "what's missing", "find gaps", "what should I work on in this repo".

• grill-docs

  Grill the user about a plan (same interview as grilling) and record it — Q→A transcript in grills/, each decision appended to the repo's decisions doc (both under skilleddocs/ by default). Use for "grill me and document it", "grill with docs".

• grill-me

  A relentless interview to sharpen a plan or design.

• 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.

• handoff-auto

  Write a handoff document for a fresh session, callable by the model. Use from 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 new idea against a repo's existing plan (issues, board, roadmap, decisions), then record the outcome. Use to pitch an idea; update-progress calls it for handoff deviations.

• divide

  Split a GitHub issue or task into session-sized issues and put them on the board. Use when a task is too big for one session or remaining work must be split off.

• kanban-setup

  Create a GitHub Projects kanban board for a repo and fill it with issues from documented work (planned, already done, or both).

• next

  Show the next work-session task from a repo's GitHub kanban board. Use when starting a work session or asking what to work on next.

• session-handoff

  End an implementation session that started from a GitHub issue — writes the handoff, records progress against the issue, moves the card.

• update-progress

  Verify a session's handoff document and update the repo's docs and kanban board from it. Run in a fresh session after session-handoff.

• lanes

  Set, increase, or decrease the parallel lanes of a meta-orchestrator run by grouping queued issues into file-disjoint streams, with a cost line and a confirm step. Use for "/lanes 3", "more lanes" / "go faster in parallel", "fewer lanes", or when meta-orchestrator setup reaches `parallel:`.

• meta-orchestrator

  Run a repo's backlog unattended as the orchestrator — planner, manager/implementer and verifier subagents per issue, merge gated on tests + CI, a ledger, and handoff to a fresh orchestrator on a budget. Use for "work through the backlog/board and don't stop", "act as the orchestrator", or "resume" a

• pair

  Run one task (issue number or free text) in an isolated git worktree via a manager subagent that owns its implementer and retries; you push and open the PR at the end. Use for "implement issue N", "pair on this", or one task on any repo, forks included.

• ponytail

  Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains abo

• pr-watch

  Watch the user's open PRs to merge — read bot and human review threads, fix valid ones via pair, reply to or resolve the rest with evidence, report CI; every push, reply, and resolve gated on a yes. Use for "watch my PRs", "address the review comments", "drive this PR to merge".

• progress-report

  Write a short progress report of what an orchestrated or long session did since the last report (never overlapping): done, what worked, what didn't, concerns, decisions made for the user, manual steps. Use for "update doc", "what's been done", "write up progress".

• remind

  Set a reminder for when an account's session or weekly limit resets, when its usage drops under a percentage, or at a time; list or cancel them.

• repo-scrub

  Scan a GitHub repo's full history for secrets and large files, scrub what the user picks, rewrite history safely, then flip it private → public.

• repo-showcase

  Make a repo public-facing on its working tree — README rewritten around outcome and demo, stale docs pruned, outdated claims fixed, secrets and private names found, GitHub metadata proposed — then hand off to /repo-scrub. Use for "showcase this repo", "polish the README for public", "prep for open-s

• score-loop

  Run an unattended experiment loop that hill-climbs one rerunnable numeric score — local grader-mirroring harness, one hypothesis per commit, keep only gains beyond the noise margin, auto-revert the rest, append-only results ledger; stops on budget, deadline or plateau. Use for "improve this score",

• session-bridge

  Coordinate with another Claude Code session or agent on the same repo — snapshot its state, check for overlap, send it a gated message. Use for "check with / message the other session", "what's the other agent doing", "is anyone else touching this file or branch".

• sitrep

  Live status of this session in ≤10 lines — what's running, git state, PRs + CI, asked vs done, what needs the user, and a SAFE/NOT SAFE close verdict. Use for "how's it going", "status update", "what's running", "can I close this".

• spend-gate

  Gate any billable action (GPU pods/instances, paid APIs or tiers, cloud credits) behind a cost estimate, a live balance check, and an explicit yes for that action. Use before any create/deploy on a paid provider (runpodctl, vultr-cli, aws/gcloud/az, modal, provider MCP create/deploy/run/start/update

• switch

  Move this conversation to another Claude account (the previous one, or one by name), or set up, add, remove, rename and list accounts.

• teammate-brief

  Write an onboarding document for a person joining or picking up a project — what it is, setup steps verified by running them, env var names and where to get them, tasks with "done when", owners, don't-touch list. Use for "brief my teammate", "onboarding doc for X", "hand this project to someone".

• wayfinder

  Plan an effort too big for one session as a map of decision tickets (GitHub issue + sub-issues) and resolve them one per session until the way is clear, then hand off to divide.

Subagents (5)

• README
• implementer

  Implements one well-specified issue from a kickoff brief on its own branch, commits small, runs the tests, and ends with a handoff document. Cannot push protected branches or merge PRs (hook-enforced); local merges are left to the caller. Use for scoped implementation delegated by an orchestrator or

• manager

  Owns one task inside a worktree — briefs an implementer subagent, reviews its diff and reruns tests itself, restarts a fresh implementer from skilleddocs/HANDOFF.md when one stalls (≤3 rounds). Never pushes or merges. Use from pair, or from meta-orchestrator with shape pair.

• planner

  Picks the next issue from a repo's board, applies the run's scope exclusions, decides whether to divide, rates its size, recommends a shape and model, and returns a ≤40-line kickoff brief. Read-only. Use when an orchestrator needs the next task briefed.

• verifier

  Verifies an implementation session: checks its handoff's claims against git, tests and CI, reviews the diff, updates docs/board/issues, reconciles deviations via consult-plan, and ends with the next task. Use after an implementer or manager finishes.

Hooks (1)

• PreToolUse

  for p in python3 python py; do "$p" -c "import sys; sys.exit(sys.version_info < (3, 8))" </dev/null >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/agents/hooks/guard-git.py" --plugin; done; grep