go-task

Files (1)

• SKILL.md

SKILL.md (first lines)

# Go Task

Pick the smallest mode that fits:

- `go-flow`: default for normal, unclear, cross-file, or risky code changes.
- `go-fast`: small, localized, low-risk changes.
- `go-pm`: product review and scope shaping before implementation.

## Shared Rules

- Scan first; ask only for blockers.
- Preserve unrelated work.
- Do not create an Issue unless the user or repo process requires it.
- Report progress in chat for long tasks.
- Do not mark work done, create PR, or merge until the required gates pass.

## Required Gates

Run these as hard gates, not optional reminders:

1. `after_execute`: correctness review, regression review, and over-engineering review. Use `ponytail-review` when available.
2. `before_pr`: inspect diff and run the smallest relevant build/test/lint command. Fix compile or test failures before opening PR.
3. `before_merge`: confirm checks are green and review findings are resolved. Merge only when requested or clearly included in the task.

If a gate cannot run, stop and report why.

## Mode Routing

- Use `go-flow` unless the user explicitly asks for speed and the change is low risk.
- Upgrade `go-fast` to `go-flow` when the work touches migrations, permissions, auth, payment, data deletion, public contracts, or broad refactors.
- Use `go-pm` when the user asks to analyze, shape, or judge a requirement before coding.

From zhengchalei/go-task, MIT.

More from zhengchalei/go-task