hcb-dev

Plugin hcb-dev from marketplace hacker-cb-plugins in hacker-cb/claude-code-plugins. Commands read from the repo's manifest — 6 days ago.

Skills (22)

• backlog-survey

  Survey a whole slice of the backlog and say what to work on: read every open issue of a milestone, a label or the repository, verify each against the code, tier them by importance, draw the dependency graph and the parallel layout of candidate batches, and recommend what to take next. Use when the u

• claude-review

  Review a change with Claude's own finders — one agent per angle of the rung and, where the session can launch agents, every Critical and Important candidate the rung's budget reaches checked by an independent verifier — over the range and at the rung (medium or high) the caller fixes. Use when a pip

• codex-review

  Review a change with Codex — OpenAI's coding agent. Use when the user or a pipeline asks for a "codex review", or wants a second opinion on a change from an engine other than Claude. Review-only: returns the findings and never fixes anything. For Claude's angles in the same round, use `hcb-dev:multi

• dependency-versions

  Use when adding or updating a dependency, bumping or pinning a package version, editing a dependency manifest (package.json, Cargo.toml, pyproject.toml, go.mod, Gemfile, requirements.txt, …), choosing a Node.js runtime version, pinning a GitHub Actions version, or setting up / editing .github/depend

• findings-pass

  Rule a run's findings cold and together — verify each one independently, decide the outcome it ends in, and show them all in one table whose every row says whether it was verified. Use it once a session's work is done and findings it did not fix are still standing, its own or ones reported to it; wh

• git-cleanup

  Manual-only. Sweep the git residue work leaves in this repository — merged and orphaned branches, stale or abandoned worktrees, dead upstream tracking. Two modes, given as the argument: (S) `session` — only the branches and worktrees this session created, run before closing it; (A) `all` — everythin

• github-pr-workflow

  Drive a GitHub pull request from a finished feature branch all the way to a merged PR, looping on CI and Copilot findings until it is mergeable and then merging it on the authorization it was given — absent one, it stops at ready and asks, and it never merges on its own initiative. Use this skill wh

• implementation-workflow

  Turn one or more tasks — free-text asks from the conversation, or GitHub/GitLab issue/ticket numbers — into implemented, reviewed work. Use it at the START, when there is something to build and no code exists yet: "сделай issue #42", "do these three tickets", "build this spec", "implement this and o

• issue-tracking

  Keep deferred work in the forge's issue tracker, GitHub or GitLab — open one, update one, classify it, decompose it, close it. Use it when the user asks to file, update or triage an issue, ticket, bug or piece of tech debt; when something surfaces outside the current task that will not be fixed now

• label-taxonomy

  Set up or rework a repository's whole label set and relabel what carries it: read every label and every issue, change request and discussion that holds one, propose the families, classify every carrier in batches, then rename, create, edit, relabel and delete on the user's word and verify the result

• master-session

  Run this session as the coordinator of an epic built by parallel sessions. Use when the user assigns the role ("ты — мастер-сессия", "координируй реализацию", "разбей на волны/батчи и веди их") over an epic, a milestone or a named body of work; when a wave plan must be drawn or redrawn; and when a s

• multi-review

  Review the current change with hcb-dev's review round — Claude's finders and Codex, and security where the caller asks for it — and report the findings and what each source actually covered. Use when the user asks for a review of the change ("прогони ревью", "review this", "second opinion on this di

• seeding-gitignore

  Use whenever a `.gitignore` at any depth is created or edited, when a repo is initialized (`git init`), and before every commit — check what is about to be staged and ignore local artifacts instead of committing them. Also use when the user asks to ignore `.DS_Store`, `.claude/settings.local.json`,

• session-dispatch

  Work this session is NOT going to do, turned into an order to paste into another session: a build to run there through `hcb-dev:implementation-workflow`, or an investigation whose deliverable is recorded tracker state or a verdict. Use when the user wants a prompt for a new session, hands fixes or a

• session-handoff

  What this session FINISHED, turned into a prompt to paste into another session — in whatever form the result took: code on a branch or in a change request, an investigation that changed no files, issues rewritten or reclassified, a documentation change. Carries the result, the complete list of chang

• session-plugin-refresh

  Re-read the skills and references this session works under after its plugin moved, and reconcile what the session already did with what those files now say. Use when the user reports the update — "plugin was updated", "плагин обновился", "перечитай скиллы и референсы", "обновись под новую версию" —

• shipping-workflow

  Take one finished slice to completion — local review across every reviewer, the fixes it turns up, a coverage check, then completion by mode: merged locally into its parent branch, or an open change request. Use it when the user says to ship, finish, open a PR or MR, get this merged, or merge it loc

• status

  Say where the work stands right now, re-read rather than recalled, in whichever role this session holds — an epic and its batches, one batch of a wave, or a standalone run and its slices — and, for any session handed an epic number, that epic's state read from its ledger; with none named, which epic

• sync-base

  Check whether this branch's base has moved and, where it has, bring the branch up to date with it — a fast-forward where the branch has nothing of its own, a rebase by default, a merge where its history may not be rewritten, `--autostash` over a dirty tree — then read what arrived against the work i

• wave-dispatch

  Turn a planned batch of work into launched parallel sessions — each started by this session as a Helmhouse session under it where Helmhouse runs it, as a chip where the host offers one, or as a fenced block to paste where neither does; the wave order inside. Use when a coordinating (master) session

• wave-refresh

  Recompute what parallel work can safely start right now: pin the base and the moment the tracker was read, measure the ground the running batches hold, take the delta since the last reading, rule what clears it, and say how many batches are actually free — then hand what the user approves to the lau

• wave-worker

  The receiving side of a wave order: this session was started — from a chip, a pasted block, or a launch by its master — with a batch dispatched by a master session ("Batch … from its master session", "волна/батч из мастер-сессии", "act per hcb-dev:wave-worker"). Governs the engagement around the bui

Similar plugins