development-workflow

Plugin development-workflow from marketplace ben-everly in ben-everly/claude-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (24)

• bug-report

  Use when asked to write up a bug as a filable report.

• commit-steps

  Use when a settled change should be laid out as an ordered list of commits a

• commit

  Use when you want to commit current changes. Accepts optional hint text to

• conventional-commits

  Use when creating git commits or writing commit messages.

• decompose

  Use when a change, feature, or issue feels too big to build or ship in one go

• design-doc

  Use when the user requests a Google-style design doc.

• estimate

  Use when a ticket, issue, or described change needs an estimate or size.

• execute-plan

  Use when you have a written implementation-plan and want it executed task by

• feature-request

  Use when asked to make a feature request.

• finding-report

  Use when asked to write up a finding you already have the investigation for —

• finish-branch

  Use when finishing a completed local branch — pushing it, opening the PR/MR

• gather-review-issues

  Use when a user asks to find, collect, or list the feedback from a code

• implement

  Use when implementing a single, well-scoped change that has already been

• implementation-plan

  Use when the user requests a commit-by-commit implementation plan a fresh

• inline-review

  Use when the user wants a quick review of the current working diff (typically

• investigate-issue

  Use when you need to judge whether a single claim about the code is a real

• pr-authoring

  Use when writing or drafting a GitHub pull request's body.

• prioritize

  Use when prioritizing tickets or deciding which to work first.

• quoting

  Use when a document you are writing shows text someone else wrote.

• reproduce

  Use when a failure resists reproduction — an intermittent flake, a test that

• review-followup

  Use when working through review feedback systematically — phrasings like "go

• tdd

  Use when implementing any testable change and you want test-first discipline.

• technical-writing

  Use when writing or revising any formal technical document, one meant to stand

• ticket-tracker

  Use when a ticket must be filed in, moved between the columns of, or

Subagents (2)

• investigator

  Dispatched by the investigate-issue skill to judge one claim about the code

• technical-writer

  Use when a technical document has to be drafted by a separate context from a

Similar plugins