# Workflow Checklist

Use this checklist every time the `code-submit` skill is invoked.

## 1. Inspect and plan

- Understand the user request.
- Derive `<change-slug>` from the task title.
- Inspect repo structure and relevant modules.
- Identify likely validation commands.
- Identify whether the change has UI, API, CLI, or internal-only impact.

## 2. Implement

- Make focused code changes.
- Keep changes cohesive and easy to review.
- Add comments only for non-obvious logic.

## 3. Validate

Run what the repo supports:

- tests
- lint
- typecheck
- build
- targeted manual verification

Validation is **informational, not blocking** for draft PR creation.

## 4. Gather report evidence

Collect:

- `git diff --stat`
- `git diff --name-only`
- key code excerpts
- architecture notes
- screenshots / recordings / terminal output as applicable
- any failing command output

## 5. Produce HTML report

Create `.submissions/<change-slug>.html` with:

- executive summary
- changed files grouped by theme
- architecture fit
- end-to-end flow
- visuals
- non-obvious code explanations
- validation + risks

## 6. Commit and PR

- Create or switch to a feature branch whose name stays close to the task title.
- Commit with a descriptive message.
- Write `.submissions/<change-slug>.pr.md`.
- Use the task title as the basis for the PR title.
- Run `gh pr create --draft`.

## 7. Final response

Return:

- report path
- branch
- commit
- PR URL
- validation summary
- remaining caveats