project-kit

Plugin project-kit from marketplace project-kit in cilaman/claude-project-kit. Commands read from the repo's manifest — 13 days ago.

Skills (7)

• bl-bug

  Triage a finding into the GitHub issue queue — take a bug report (user's own words, a feedback-widget email, a log excerpt, a stack trace), trace it to the place in the code against fresh origin/main, decide whether it really is a defect, rule out duplicates and already-fixed versions, and file one

• bl-finish

  Close a backlog item — run the sieves green tests cannot replace (screenshots, targeted adversarial review, mutation of your own new tests) BEFORE saying done, walk the Definition of Done, write `status:` and `result_note:`, move the spec file to `backlog/done/`, let `check_repo.py --rebuild-all` wr

• bl-start

  Start work on a backlog item — create or take over the GitHub issue (its number IS the item id BL-NN), decide whether a spec file is needed, claim the task with a pushed claim commit and open a draft PR with `Closes #NN` filled in. Use whenever work begins on anything that will end in a pull request

• decision-record

  Write a decision record in docs/decisions/ — header block (Status/Parent/Origin/Scope with an explicit "does NOT"), the question, considered options with their cost, the decision, consequences and what it leaves undecided; or extend an existing decision with a dated addendum or a superseding record

• guard

  Turn an invariant that lives only as prose (a rule in CLAUDE.md, a decision, a docstring, a review finding) into a machine guard — a test or a `check_repo.py` check — with an anti-vacuum test, the reverse direction (named exceptions with reasons, where empty and orphan rows fail), a mutation proof t

• project-init

  Initialise a repository with the project-kit method — CLAUDE.md with hard rules backed by guards, docs map and decision records, backlog where BL-NN is the GitHub issue number, claim protocol, generated indexes (BACKLOG.md, DONE.md, tasks.tsv), CI and task-lifecycle workflows, issue forms, labels, a

• steward

  Get a pull request to green — what to verify before a push and how much of it (derived from the diff, not guessed), how to resolve conflicts in generated files (regenerate, never merge by hand), what each CI step means and how it is fixed, what must never be done for a green check, and how to handle

Hooks (1)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/guard_generated.py"

Similar plugins