Skip to content

clockgrove/pendulum

v0.10.3MIT

Label a GitHub issue and walk away: a coding agent (Claude Code, Codex or Copilot CLI) plans, builds and opens the pull request, a second agent reviews it, and your CI and merge queue land it.

pendulum-deliver-pr

Internal: the last stage of a Pendulum worker run on an Objective, after pendulum-prove-acceptance, loaded only when a Pendulum task card or answer pass names it. Rebases on the default branch, writes the one PR's title and body, answers each reviewer comment once, writes the exit record and stops; Pendulum pushes, opens the PR and posts the replies.

pendulum-doctor

Check that this repository, its GitHub settings, its model credential and its runner are ready for unattended Pendulum runs, and name the fix for each failure; changes nothing. Use when the user asks whether Pendulum is set up, why Objectives Block at the first step, or before enabling the workflow. Not for applying the fixes (pendulum-setup).

pendulum-file

Write, refine and start Pendulum Objectives: turn what the user wants built into a GitHub issue with a goal and acceptance entries, created on the user's yes started (pendulum:objective) or as a draft (pendulum:draft); or, by issue number, refine or start a draft. Use when the user asks to file, draft, refine, keep working on or start a Pendulum Objective, or asks Pendulum to build something. Not for starting over one that already ran (pendulum-restart), resuming a Blocked one (pendulum-status) or running one on this machine (pendulum-run).

pendulum-handover

Apply the workflow change Pendulum handed over on an Objective (the pendulum:handover label, Pendulum's hand-over comment): put it on a new branch with pendulum handover <issue>, show the user the diff, and only once they have read it and said yes, commit, push and open its pull request with --push. Use when the user asks to apply, take or push a Pendulum workflow hand-over. Not for the Objective's own PR, which Pendulum delivers itself.

pendulum-implement-split

Internal: the second stage of a Pendulum worker run, loaded only when a Pendulum task card names it. Implements the plan's checklist with implementer sub-agents on the pinned model, runs disjoint-file items concurrently, integrates once, and splits an Objective too large for one session into sequential PRs.

pendulum-kick

Kick the Pendulum Action's dispatcher now, on the user's yes: preview what it would start and its spend caps, then dispatch .github/workflows/pendulum.yml for the whole queue or one Objective, rather than wait for its next event or ten-minute tick; without the workflow, explain the harness-cloud path for this harness. Also names the three off-machine routes and how an Objective moves between local mode and the Action. Use when the user asks to kick or run the Pendulum dispatcher or the Action's queue now, or what running off this machine takes. Not for working Objectives on this machine (pendulum-serve, pendulum-run) or seeing what the queue is doing (pendulum-status).

pendulum-objective-plan

Internal: the first stage of a Pendulum worker run, loaded only when a Pendulum task card names it. Reads the Objective's issue, writes the plan before any code, records every assumption and applies the Question rule.

pendulum-prove-acceptance

Internal: the third stage of a Pendulum worker run on an Objective, after pendulum-implement-split and before pendulum-deliver-pr, loaded only when a Pendulum task card names it. Proves every acceptance entry through the repository's real path per its testing guide, runs the validation and test-budget commands, applies the base-failure rule and iterates locally before the hand-off.

pendulum-report

Report what Pendulum's Objectives cost and how many tokens they used, over a period or a set of Objectives, from pendulum report --json: totals by billing kind, runs of unknown cost with their reasons, breakdowns by stage, pass, model, harness and Pendulum version, per-Objective rows, review findings and their outcomes, and hot spots, every figure precomputed; presented as a table, chart, page or document as the user asks; on request, model-usage proposals. Use when the user asks what Pendulum cost, where its spend or tokens went, which model to try where, or for a cost report, chart or dashboard of its runs. Not for one Objective's walk-away scorecard row (pendulum-score) or what is running now (pendulum-status).

pendulum-restart

Restart one Pendulum Objective from its issue's current text, in any state, on the user's yes: applies the pendulum:restart label, which stops a running stage and discards the earlier plan, branch and pull request. Use when the user asks to restart, redo or start over a Pendulum Objective, or says one was built from the wrong text. Not for pausing one (pendulum-stop), or letting one go on after a fix or an answer (pendulum-status).

pendulum-review-here

Review one Pendulum Objective's PR of the current repository by number: in this session with the reviewer's skill, posting one comment-only pass of line-tied findings as the user only once they have read it and said yes; or, on their yes, with local mode's sandboxed review stage (pendulum review <pr> --wait). Use when the user asks to review a Pendulum PR. Not for answering a review's comments, which the worker does (pendulum-run).

pendulum-review-pr

Internal: the Pendulum reviewer's instructions, loaded only by Pendulum's reviewer job, its reviewer agents and the pendulum-review-here skill. One pass of line-tied review comments on a Pendulum PR (an Objective's pull request), each naming the acceptance entry or repository rule it concerns, with behaviour-changing assumptions flagged; no verdict, no approval, no request for changes, no refusal.

pendulum-run

Run one Pendulum Objective of the current repository on this machine by issue number, on the user's yes: by default in local mode (pendulum run <issue> --wait: sandboxed, the Action's worker, reviewer and merge), or with --here in this session itself, handing the branch to Pendulum to push only on a second yes. Use when the user asks to run, work or build one Pendulum Objective on their machine. Not for working the whole queue (pendulum-serve) or kicking the Action's dispatcher (pendulum-kick).

pendulum-score

Build or print the Pendulum scorecard: one row per Objective with the four job-one numbers (walk-away, solution quality, operator minutes, dollars per merged Objective), read from the issue, the PR, the job log and the uploaded usage artifact; its reference says how each is measured, its unit and basis per harness. Use when the user asks for the scorecard, the cost of an Objective, whether an Objective walked away clean, or how Pendulum runs are scored. Not for what an Objective is doing now or why it is Blocked (pendulum-status).

pendulum-serve

Start Pendulum's local loop for the current repository on this machine (pendulum serve) on the user's yes: it takes the Objectives labelled pendulum:local (every one where no Action is active), works, reviews and merges them in sandboxes on this machine's harness login, and resumes its own paused work first; also supervises the queue with pendulum wait. Use when the user asks to run Pendulum locally, serve, or work the queue on their machine. Not for one Objective by number (pendulum-run) or kicking the Action's dispatcher (pendulum-kick).

pendulum-setup

Install Pendulum in the current repository, one step at a time on the user's yes: add .github/workflows/pendulum.yml through a pull request, create the GitHub App, and apply the merge queue, labels, Project board and a read-only default workflow token; or set up local mode on the user's machine. Use when the user asks to set up, install or configure Pendulum for a repository. Not for checking whether it is set up (pendulum-doctor).

pendulum-status

Show what Pendulum is doing in the current repository, read-only: each open Objective's state and route, and for a Blocked one or a Question the reason and the way on (resume, answer or restart), taken only on the user's yes. Use when the user asks what Pendulum is doing, what is running or queued, why an Objective is Blocked or stuck, or how to answer or resume one. Not for whether the repository is set up (pendulum-doctor) or the scorecard of finished Objectives (pendulum-score).

pendulum-stop

Stop one Pendulum Objective on the user's yes: removes the issue's pendulum:objective label, which ends its running stage and keeps every tick and loop from picking it up; its branch and pull request stay. Use when the user asks to stop, halt or cancel one Pendulum Objective, or says one should not run. Not for starting one over from its issue's current text (pendulum-restart).