← ClaudeAtlas

agent-workerlisted

Work a coding task end to end in a repo — learn the project's own rules first, branch (or an isolated worktree when asked) and ask before touching a non-main branch, build in milestones, run the project's gate after every chunk, prove each finished milestone actually runs, commit in plain language, never push and never merge. Use when the user hands over a task to implement, fix, or refactor in a repo ("work on this", "implement this", "fix this", "build this feature", "take this ticket"), or invokes /agent-worker.
Xenoneqq/claudified-workflow · ★ 1 · AI & Automation · score 74
Install: claude install-skill Xenoneqq/claudified-workflow
# agent-worker How to carry out work in a repo. This is the *process*, not the code style. **The repo outranks this file.** Wherever a project documents its own branching, worktree, commit, or review workflow — in `CLAUDE.md`, `AGENTS.md`, `CONTRIBUTING.md`, a PR template, a `doc/` page — follow that instead of the corresponding section here. Use these rules as the default only where the project is silent. Two things this skill never does: **push** and **merge**. Not once, not "just this branch", not when the user seems to want speed. Finish the work, leave the branch, say what is on it. ## 0. Learn the project before writing anything Never guess at conventions a repo has already written down. Before the first edit: - Read `CLAUDE.md` / `AGENTS.md` at the root and in any directory you will touch. - Read whatever those files point at (`doc/`, `docs/`, `CONTRIBUTING.md`, a design doc, a code-style doc). If a project doc says "read this before touching UI", read it. - Find the gate commands: `package.json` scripts, `Makefile`, `justfile`, CI workflow. Typecheck, lint, format check, tests — whichever exist. - Read 2-3 files near the change to match the local idiom. If the project has no written rules, follow the surrounding code and say so in the recap. ## 1. Branch — or a worktree when asked **Default is a branch in the current checkout.** Do not create a worktree on your own initiative; it moves the user's work somewhere they did not ask for. - On `main` / `master`: c