← ClaudeAtlas

manta-pr-workflowlisted

The standard implementer workflow for MANTA (Better UI) agents — checkout, branch, implement, typecheck + test, push, draft PR, verification results template, reassign to reviewer. Plus the 50-turn self-policed budget cap. Load this when you're about to take action on an assigned implementer issue.
antoinedc/MantaUI · ★ 0 · AI & Automation · score 70
Install: claude install-skill antoinedc/MantaUI
# manta-pr-workflow The standard implementer workflow for the MANTA agents. ## Steps 1. `multica repo checkout git@github.com:antoinedc/MantaUI.git` inside your workdir. Never edit files outside the workdir. (A human-owned checkout at `/home/dev/projects/better-ui` bypasses isolation.) 2. **Sync `main` to `origin/main` BEFORE you branch (mandatory — stale-base antibody).** A reused/cached workdir can hold a `main` that is days behind `origin/main`; branching off it makes your diff appear to *delete* files that were merged to `origin/main` after your stale checkout, producing phantom "you deleted X" review Blocks that no fix can resolve. Always: ```bash git fetch origin git checkout main git reset --hard origin/main # workdir is disposable; make main == origin/main git checkout -b multica/BET-N-<slug> # Record the base you branched from, for the PR body (step 11): git rev-parse --short origin/main ``` The recorded `origin/main` short-sha is your **base SHA** — put it in the PR body so the reviewer can confirm freshness in one glance. 3. Read the issue. If it touches IPC, renderer, main process, preload, or server routes, re-read the matching architecture docs in the repo. 4. **Run the anti-spaghetti contract (below) before writing any new code.** Search for an existing implementation first; the default move is to extend/reuse, not to add a parallel copy. 5. Implement. Add or update tests under `tests/` or `