Skip to content
Agentmart
Submit a tool

brutal-worker

Own one exact BRUTAL.md task or review finding through claim, isolated implementation, verification, stacked pull request publication, and an uncapped…

Skill by sssemil

IndexedMIT★ 2
Write a review

Chalk Labs

Need help deploying brutal-worker?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/sssemil-brutal-worker

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Own one exact BRUTAL.md task or review finding through claim, isolated implementation, verification, stacked pull request publication, and an uncapped material-correctness review/fix loop. Managed workers execute one phase at a time with fresh context.

Use cases: productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/brutal-worker

What's inside

Skill name
brutal-worker
Description
Own one exact BRUTAL.md task or review finding through claim, isolated implementation, verification, stacked pull request publication, and an uncapped material-correctness review/fix loop. Managed workers execute one phase at a time with fresh context.
License
MIT
Instructions
110 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Brutal Worker

Complete one exact work item and its pull request. Never select a replacement.

## Required Context

Always require the stable task reference and read applicable repository rules.
Read `../brutal-shared/integration-resolver.md` and
`../brutal-shared/support/contracts.md`. Reuse a managed assignment’s validated
work-store/code-host identities, canonical local root, worktree, branch, and
base; resolve only missing data needed by the current phase.

For standalone work, also read
`../brutal-swarm/references/parallel-execution.md`, create or resume the isolated
worktree with `../brutal-swarm/scripts/worktree_manager.py`, and read
`../brutal-inf-fix-loop/SKILL.md` plus its source skills.

For managed work, the immutable handoff establishes assignment identity;
the phase snapshot supplies revalidated mutable state. Runtime names, logs, and
old snapshots are observational and grant no provider authority.
Read only the supplied phase context file.

## Hard Rules

- Own only the handed-off item, branch, worktree, and pull request.
- Select only `task` or `review_finding`; never implement a plan or
  investigation.
- Never merge, approve, request changes, force-push, delete a remote branch, or
  create a second pull request for the item.
- Preserve unrelated changes and edit only the isolated worktree.
- Keep the item `in_progress` until a fresh review has no CRITICAL or MAJOR.
  Then it may move to `in_review`; move it to `done` only after its PR merged.

## Managed Phase Protocol

When the prompt contains a managed phase snapshot, do only that phase and
return the supervisor’s exact result. Do not continue into the next phase.

### `work`

Read the full item, history, parent/blockers, assignment, and existing PR link.
Prove the exact claim from the expected state before changing code. Validate
worktree, branch, base branch/SHA, and branch task marker. Implement, test,
self-review, commit, push, and find-or-create the single marked PR. Return a
checkpoint with current base/head, PR, verification, and zeroed review fields.

### `review`

Read `../brutal-inf-fix-loop/SKILL.md` and
`../brutal-pr-review/SKILL.md`. Use only the exact PR/base/head snapshot and
relevant repository rules. Run one fresh `material_convergence` pass. Return
counts for all severities, review id, queued/unhandled counts, summary status,
and residual MINOR/NIT findings. Exit after the checkpoint.

### `fix`

Read `../brutal-inf-fix-loop/SKILL.md` and
`../brutal-pr-finding-fixer/SKILL.md`. Drain the full generated all-severity
queue for the supplied review occurrence, verify, push, re-read base/head, and
return a checkpoint. Do not start a review.

If `work` or `fix` hits a merge/rebase conflict, preserve the worktree and
return `blocked` with the exact recovery state.

### `handoff`

This phase is reached only after a fresh review has zero CRITICAL and zero
MAJOR. Revalidate PR identity, base/head, task ownership, queue state, and
required checks. Reuse same-head verification only when the complete base/head
snapshot still matches and checks still pass; otherwise rerun it. Record
changed files, commands/results, commits, PR/base, review id, completion kind,
and residual MINOR/NIT findings on the task. Move it to `in_review` and return
terminal `clean` with `zero_findings` or `materially_clean`.

### `complete`

After a matching PR is verified merged, record acceptance, move the item to
`done`, and return terminal `clean` with `completion_kind: merged`. This is the
only preassigned phase that replaces the scheduler’s post-merge `finalize`
action; never use `finalize` as a managed worker phase.

The supervisor alone derives legal phase transitions. A fresh phase uses fresh
execution context. The tmux adapter resumes its exact Codex thread only when an
attempt was interrupted in the same phase. Return `blocked`, `canceled`,
`claim_lost`, or `failed` with exact recovery state on hard stops.

## Standalone Lifecycle

1. Read and claim the exact item. Resume a matching open PR/branch; complete a
   matching merged PR; block on closed-unmerged or identity mismatch.
2. Confirm the isolated branch/base and implement the smallest verified change.
3. Commit and push normally. Find the PR by exact marker and head before
   creating one against the handed-off base:

       <!-- brutal-worker:v1:<stable-task-ref> -->
       Source: brutal-worker
       Work item: <stable ref or URL>
       Parent: <stable ref or none>
       Blocked by: <stable refs or none>
       Stack base: <branch and blocker ref or root>
       Verification: <commands and results>

4. Run `$brutal-inf-fix-loop` until materially clean, perform the `handoff`
   checks above, update the item, and move it to `in_review`.

Redirect verbose builds, tests, diffs, and provider output to run-local
temporary logs. Report command status and duration. On failure, include only
the last 200 lines or 16 KiB, whichever is smaller.

From sssemil/SKILLS, MIT.

More from sssemil/SKILLS

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Jul 22, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from sssemil

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get brutal-worker running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying brutal-worker?

CallGet help
Cite this page

brutal-worker skill. Agent Mart. https://agentmart.dev/skills/sssemil-brutal-worker (last updated 2026-10-24)