development-discipline

Plugin development-discipline in jwilger/ai-plugins. Commands read from the repo's manifest — 2 days ago.

Skills (11)

• change-preflight

  Use when preparing to edit a feature, bug fix, refactor, documentation or configuration update, packaging or release work, migration, operational change, or other substantive repository change; classify it before editing and explicitly decide all ten surfaces from repository or supplied evidence.

• ci-failure-follow-up

  Use when a pushed CI run fails or before later work or pushes; coordinate multiple agents through Tiber's CI-recovery owner/lease, reproduce the exact recovery record, permit only a causal repair or unchanged-SHA rerun, and require terminal success.

• delivery-workflow

  Use when choosing whether and how verified work should be committed, pushed, reviewed, and delivered under a repository's local workflow policy; frequent small commits apply in every mode, while local-only commits remain local.

• development-workflow

  Use when a development request needs lifecycle routing for diagnosis, implementation, review feedback, PR or MR creation, readiness, CI failure, verification, or delivery.

• final-review

  Use when completing or claiming readiness for local-only changes, a branch, pull request, merge request, or merge-to-main; final review applies even when repository policy forbids publishing, including scope growth, proposed work splits, and medium-risk review-budget checkpoints.

• rationale-commit-messages

  Use when writing, reviewing, or proposing a Git commit message for authored development work, including after an implementation increment is complete.

• receiving-code-review

  Use when receiving human, automated, GitHub, CodeRabbit, or other review feedback before changing code.

• systematic-debugging

  Use when a bug, failing test, broken command, unexpected output, or confusing runtime behavior appears.

• test-driven-development

  Use when implementing a feature, bugfix, production behavior change, removal, or refactor to decide whether RED applies and, when it does, work from one failing public behavior test at a time.

• verification-before-completion

  Use when claiming work is done, fixed, passing, ready, reviewed, committed, or safe to merge.

• writing-skills

  Use when creating or editing skills in this marketplace or preparing skill behavior fixtures.