An agent skill · demonstrated in Amp Orbs

AMP Fit.

AMP Fit reads what a repository’s owner keeps coming back to, from commits, open pull requests, plans, rule files and the owner’s comments on its earlier pull requests, finishes that one thing on a branch with the gap’s check run before and after, and returns exactly one of two things: a single pull request whose body says what is unresolved, who decides it and what merging authorizes, or a one-minute status of what is waiting on the owner and why.

AMP Fit / regular Orb

Six paired runs, same commit, same minute.

Each pair launched a regular Orb and an AMP Fit Orb on the same repository at the same commit, within a minute of each other, in the same model and mode. Only the message differed: the regular Orb was told to find the most useful thing to do and open a pull request.

Where grounded work existed, both Orbs delivered. Where it did not, the regular Orb opened a pull request every time and the owner wanted none of them; one edited files the owner had frozen. AMP Fit opened nothing and said so. Collected 21 September 2026 on the skill version before that rewrite; a seventh pair was excluded because the regular Orb loaded the skill on its own. The repositories are the author’s own and the author graded every run.

Over six pairs	Regular Orb	AMP Fit
Pull requests opened	6	3
Merged	2	3
Not wanted by the owner	3	0
Closed as a duplicate	1	0
Correctly opened nothing	0	3

The skill behind the work.

Read the skill ↗

Finish the thing the owner of this repo keeps coming back to and has not finished, and return it as one pull request they can merge; anything else you notice goes in one line at the bottom of the PR, not in the diff. When nothing is grounded, return a status the owner can act on in a minute, not a pull request they have to review.
The assignment, verbatim: the opening sentence of the 65-line skill every pass loads.

Outcome one

One pull request

When something grounded is left to finish. Opened from its own branch, never the default branch, under 400 words, with exactly these headings in this order:

What this finishes
Why it matters here
How it was done
What I ran, what I did not run, opening with Before: and After:
What is unresolved, each item naming who decides
What merging authorizes, exactly one thing

Then a Noticed / frozen / rules read line, and the ledger line the owner grades.

A real one: food-bridge-app #19, merged 2026-09-21

Stop promising cross-device backups after account sign-in What this finishes Account-status honesty following #15, #17, and #18, all merged 2026-09-21. #18 explicitly records unfinished restore/continuous backup, but account screens still guaranteed both, even after failed uploads. Why it matters here People no longer get told their progress is recoverable on another device when signing in cannot provide that recovery. How it was done Signup, sign-in, success, and management disclose unavailable cross-device restore/automatic backup and the risk of clearing browser data. Authentication confirms only sign-in. Existing uploads and local data behavior remain unchanged; this does not implement sync. Followed BUILD-PLAN's engine fence, AUTH-BUILD-BRIEF's auth boundaries, and MAINTENANCE-AGENT-PROMPT's frozen schema/eval/data/marketing exclusions. Honored Daniel's 2026-09-20 ruling: “audit X3 is not work I want done now”. What I ran, what I did not run Before: node --test yonder-app/scripts/account-signout.test.mjs — 9 passed, 7 failed against new assertions. After: same command — 16 passed, 0 failed, including successful, pending, failed, and non-persisted uploads. - node --experimental-test-module-mocks --test yonder-app/scripts/*.test.mjs — 95 passed. - node yonder-app/scripts/auth-ci-guard.mjs; git diff --cached --check — passed. - App-directory npx --no-install wrangler deploy --dry-run --outdir /tmp/amp-fit-28-bundle — passed. - agent-browser --session fit28 click/fill/wait/eval/snapshot/screenshot — mocked upload-failure success checked; desktop/narrow screenshots inspected. Management required programmatic click because its existing link is hidden; initial pointer check timed out. Browser errors empty. - npm ci --ignore-scripts — installed; six existing vulnerability warnings. - No production deployment, shared-data writes, real cross-device recovery, or Safari/Firefox checks. What is unresolved Daniel decides deployment timing. AGENT-COMMS.md is absent; Daniel supplies it if coordination requires it. What merging authorizes Merge this account backup-assurance correction only. Noticed: sync/carry-over remains unfinished; account link stays CSS-hidden; frozen: none identified; rules read: CLAUDE.md, yonder-app/CLAUDE.md, BUILD-PLAN.md, components/PORTFOLIO.md, AUTH-BUILD-BRIEF.md, MAINTENANCE-AGENT-PROMPT.md. ledger: | 28 | 2026-09-21 | iamdanielkitchen/food-bridge-app | inferred: stop false account backup assurances | orb-high | T-01a0c53c-4f00-754a-8426-5152b8d88abd | https://github.com/iamdanielkitchen/food-bridge-app/pull/19 | | | | | |

Outcome two

A one-minute status

When nothing mergeable is grounded. No pull request is opened; the final message is under 250 words, one line per item:

empty: why nothing is grounded, or needs-decision: the exact question and who decides
Because: the evidence, each item with its file or commit and its date
Options: proceed as directed, retire the direction, or a third way
Considered: up to three candidates and why each was declined
Waiting on you: open pull requests and decisions, each naming who acts
Noticed: / frozen: / rules read:
Checked: the commands that ran

Then the same ledger line, with the outcome empty or needs-decision.

A real one: interface_v0.1, pass 29, 2026-09-21

empty: Repository operations are shut down; no currently wanted work grounds a pull request. Because: Daniel closed PR #1 unmerged on 2026-09-21: “operations on this repository are shut down, so the finish-line verification work is not wanted now.” This supersedes ACTIVE_FINISH_LINE_PLAN.md, created July 30 and last edited August 1, 2026. Options: none. Considered: Terminal-baseline verification—declined by Daniel on PR #1; unfinished rehearsals/final run—covered by the shutdown; correcting the stale plan—Daniel explicitly retained that responsibility. Waiting on you: No open PRs. Daniel owns recording the shutdown in the repository; nothing requires action to leave operations stopped. Noticed: Referenced CLAUDE.md, runs/live_gapfind/GAP_BOARD.md, and runs/lead/GAP_attach_followons_post_frames.md are absent; frozen: instruction drift and deferred DRIVE pruning remain fenced by .cursor/rules/instructions-frozen.mdc and WB_DIRECTIONS.md; rules read: both .cursor/rules/*.mdc, the run-only skill, DONE, INPUTS, EXCLUDED, WB_DIRECTIONS, DRIVE, README, instruction audit, and active plan. Checked: gh pr list, gh pr view 1, gh issue list, gh run list, dated git log, file reads/existence checks, and git status --porcelain—clean worktree. No tests or live runs executed; no files changed or PR opened. ledger: | 29 | 2026-09-21 | iamdanielkitchen/interface_v0.1 | inferred: reassess unfinished finish-line work against owner shutdown | orb-high | T-01a0c53c-5c77-70e6-9fd8-5c2260a98790 | empty | | | | | |

It never writes the default branch or a file the owner marked frozen, and it never grades its own work. The owner’s comments on earlier pull requests are standing rules for every later run.

What happened in real repositories.

Read the ledger ↗

—
merged pull requests: —
owner-graded passes: —
minutes saved, owner estimate

Loading the recorded outcomes.

Inspect the recorded passes

Pass	Work / repository	Outcome	Review min

Inspect the six pairs

Pair	Repository	Regular Orb	AMP Fit
P1	portfolio-site	PR #9 · closed, not wanted	No PR · no grounded work · row 19
P2	portfolio-site	PR #10 · open, not wanted	No PR · no grounded work · row 21
P3	food-bridge-app	PR #15 · merged	PR #16 · merged · row 22
P4	food-bridge-app	PR #18 · merged	PR #17 · merged · row 24
P6	interface_v0.1	PR #1 · closed, wrong job; edited six frozen files	No PR · owner decision · row 20
P8	ecomm-support-agent	PR #2 · closed, duplicate of AMP Fit’s	PR #1 · merged · row 25

See it run.

Recorded run · 20 September 2026

portfolio-site / Finish the SMASHED running loop

The workLoading

Orb 1

Finish the SMASHED running loop

The assignment is ready.Start the demo to follow the Orb’s recorded activity, from finding the unfinished work to opening its pull request.

Ready to begin

Original Orb messages · selected excerpts · compressed timingOpen pull requests on GitHub ↗

Reach me on X or through the contact form.