go-flow

Files (1)

• SKILL.md

SKILL.md (first lines)

# Go Flow

Use TDD as the main line.

1. Scan the code and confirm only blocking requirements.
2. Find the existing test or check entry point.
3. Write the smallest failing test, or the smallest runnable check when tests are impractical.
4. Implement the minimum code to pass.
5. Refactor only code touched by the change.
6. Run `after_execute`.
7. Run `before_pr`.
8. Create PR when requested or implied.
9. Run `before_merge` before merging.

## after_execute

- Review correctness.
- Review regression risk.
- Review over-engineering; use `ponytail-review` when available.
- Fix findings before continuing.

## before_pr

- Inspect the diff.
- Run the smallest relevant build/test/lint command.
- Fix compile and test failures before opening PR.
- Disclose or isolate unrelated dirty changes.

## before_merge

- Confirm checks are green.
- Confirm review findings are resolved.
- Merge only when the user asked for merge or end-to-end delivery.

## Stop Conditions

- Stop if a gate cannot run.
- Stop if validation fails and cannot be fixed in scope.
- Stop if the task scope changed materially.

From zhengchalei/go-task, MIT.

More from zhengchalei/go-task