vouchington/vouchington-workflow

Shared workflow guidance for repository implementation: inspect local instructions, keep changes bounded, validate, and prepare reviewable commits.

Record and retrieve concise contemporaneous session findings when the repository provides a journal or blackboard service.

Configure or audit Dependabot coverage, cooldowns, package-family grouping, trusted CI, and conservative auto-merge policy for a repository.

Use before staging and committing changes to verify scope, validation, commit metadata, and local repository policy.

Author or redesign GitHub Actions workflows around event-driven orchestration, with remote-state polling prohibited.

Use when editing GitHub Actions workflows or composite actions to keep security, runner, permissions, concurrency, and validation aligned with local policy.

Search, create, update, link, or assess GitHub issues using the repository's live issue policy and taxonomy.

Bootstrap an npm package and give a human the exact commands to publish it publicly and configure GitHub trusted publishing.

Organize existing GitHub issues and pull requests with the repository's live taxonomy without inventing new taxonomy.

Use when changing JavaScript package metadata, dependencies, scripts, workspaces, or published entrypoints.

Create an evidence-backed implementation plan for a repository change or a justified no-change recommendation.

Draft or review a self-contained pull-request description with summary, root cause, validation, rollout, and issue context.

Produce a concise evidence-based retrospective for a completed task or session when local workflow provides a durable record.

Distill completed session records into a small set of verified, actionable follow-up issues.

Audit CI failures or noisy logs, identify the root cause, and recommend diagnostics-preserving fixes.

Audit GitHub labels, milestones, and path-label automation and return actionable taxonomy recommendations.

Review recently completed work and repository instructions for genuinely deferred follow-ups, then propose verified issue candidates.

Recognize a native GitHub stacked pull request and drain it from the bottom-most ready layer up, rather than waiting for the whole stack to be ready first.

Use when adding, changing, replacing, or removing static-analysis rules, configurations, fixtures, suppressions, allowlists, or repository guards.