gitlisted

## Decision Router IF committing changes with conventional messages → SHIP mode IF posting line-specific PR review comments → REVIEW mode IF loading issues or creating technical specs → ISSUES mode IF using git notes or worktrees → ADVANCED mode # Mode: SHIP Create well-formatted commits with conventional messages and publish pull requests. ## Commit Workflow 1. **Branch check:** If on `main`/`master`, create feature branch (`<type>/<scope>/<description>`) 2. **Lint:** Run pre-commit checks unless `--no-verify` 3. **Stage:** Auto-stage if no files staged 4. **Split:** If changes touch multiple concerns, split into atomic commits 5. **Message:** Generate with emoji + conventional commit format. ### Commit Conventions You MUST read `references/commit-conventions.md` BEFORE generating commit messages to ensure compliance with conventional commit types and emojis. ## PR Workflow 1. **Pre-flight:** Check for uncommitted changes 2. **Template:** Use `.github/pull_request_template.md` if exists 3. **Title:** Emoji + type + scope: `✨(scope): description` 4. **Create:** Draft PR by default, convert to ready when complete **Spawn Directives:** - **ALWAYS use the `git-preflight-checker` skill to run pre-flight checks (lint, type-check) in parallel while the main agent prepares the commit message** --- # Mode: REVIEW Post line-specific comments on PR diffs. Supports single comments and batched multi-file reviews. ### Review Commands You MUST read `references/review-commands.