| name | timb-contribution-workflow |
| description | Runs the general contribution workflow for shipping changes: follows AGENTS/CLAUDE and CONTRIBUTING guidance, writes meaningful tests, validates with `pnpm validate`, keeps docs/TODOs current, pushes changes, monitors GitHub CI, and responds to PR reviews or Cursor Bugbot comments by fixing or replying concisely. Use for "ship this," "validate and push," "handle CI," "respond to review," "fix PR comments," "follow the contribution guide," or "finish the workflow." Skip for read-only review unless the user asks to act. |
Timb Contribution Workflow
Purpose: finish work the way the repo expects, with evidence.
Run in order.
1. Read the local contract
Before changing behavior or pushing, inspect the repo's instructions:
AGENTS.md and/or CLAUDE.mdCONTRIBUTING.md- package manifests and scripts
- CI workflows under
.github/workflows/
- TODO/status docs in the blast radius
If CLAUDE.md and AGENTS.md both exist, treat them as the same class of agent instruction. If they conflict, follow the more specific local file and report the conflict.
2. Keep tests meaningful
Add or update tests when behavior changes.
For substantial coverage work, test reviews, new test layers, E2E setup, CI test wiring, or AI/agent evals, route through timb-test-strategy.
Good tests:
- exercise behavior through the public or intended boundary
- assert real outputs, side effects, permissions, rendering, data writes, or errors
- cover the edge case that would fail without the fix
- avoid tautologies where the mock simply returns the asserted value
Avoid snapshot churn, shallow implementation tests, and tests that only prove a stub was called unless the call itself is the contract.
