Routine work should not depend on knowing which person to ask. The task, repository instructions, existing contracts, tests, and this handbook should carry enough context for another volunteer to make a sound change.
The default path
- Read the task and restate the outcome in concrete behaviour.
- Read every instruction file that applies to the files you may change.
- Inspect
git statusand preserve work already in the checkout. - Find the current source of truth and its existing tests before designing a new path.
- Open a draft pull request and link it to the Wildbase Work task.
- Implement the smallest complete change that satisfies the task.
- Run focused checks while working, then the repository’s full relevant checks.
- Record what changed, what was verified, and what remains uncertain.
- Obtain review, merge through the normal path, and close or hand off the task.
If the task crosses repositories, make the compatibility order explicit before merging any part. If it touches production data, deployment, moderation, or a secret, use the operational boundary for that work rather than treating it as ordinary code editing.
What “done” means
A task is done when the requested behaviour exists, the relevant failure and accessibility states have been considered, checks pass or their limitations are recorded, documentation agrees with reality, and no required follow-up is hidden in Discord or a private note.
“Code written” is a status, not an outcome.