glorp

GitHub issue closer

From open issue
to merged.

gh-fix takes ownership of a GitHub issue and drives the whole delivery loop: code, proof, CI, merge, and the loose ends after it.

Install gh-fixRead the skill
01Read the full issue
and its context
02Open a draft PR
in an isolated clone
03Build, test, show
the finished UI
04Stabilize CI, merge,
close follow-ups

The promise

It carries the ticket across the finish line.

Give it an issue number. It checks the request and discussion history, works in a fresh clone, and makes progress visible immediately with a linked draft pull request.

Then it adds focused tests and a changelog note, captures proof for UI work, follows every required CI check, resolves what its change breaks, and merges only when GitHub agrees.

◉lsegal / glorp•••
Open

Add Sign Out button to Settings page

Issue opened by you · assigned to you

gh-fixI found the path, opened a draft, and am validating the button.
◉Pull request•••
Draft

Add Sign Out button to Settings page #309

Open while the work is still in progress

  1. Start work on issue #308draft opened
  2. Checkpoint issue #308 progresssafe to resume
  3. Add Sign Out button to Settings pageready for review

Draft means protected progress

Open early. Keep the work visible.

A draft pull request is the workbench, not a review request. It links the issue, records the branch, and gives everyone a live place to see what is underway.

As work changes, gh-fix pushes checkpoint commits at least every five minutes. If the session stops, the next agent resumes from the same branch instead of recreating the work.

Nothing falls through

A fully unbroken build loop.

01IssueRequest and context
02Draft PRBranch and checkpoints
03ProofTests and screenshots
04Green CIReruns until clean
05MergedIssue closed
06Follow-upsLeftovers become new issues
Context stays in scope

It reads the issue, comments, linked work, and direct Glorp instructions before acting.

UI changes get shown

Browser work earns representative screenshots or a recording in the pull request.

Nothing gets stranded

Actionable leftovers become linked follow-up issues, routed back into the team’s flow.

◉Pull request•••
Merged

Add Sign Out button to Settings page

3 commits · 2 checks passed · 1 screenshot

✓ Build and test Passed
✓ Deploy Pages Passed

No drive-by patches

It merges only after the checks pass.

The skill watches the current commit’s checks and reads failures precisely before making the smallest correct change. Transient failures get one automatic re-run; genuine blockers remain plainly documented on the pull request.

Proof people can inspect

Show the changed state, then name what it proves.

For browser work, the finished pull request includes a representative screenshot or recording. The caption says what changed and the proof text names the state, interaction, and check that made it trustworthy.

Proof attachedThe Settings page now shows a working Sign Out button, matching the passed browser test.
Sample screenshot of a Sign Out button on a Settings page
Proof: the Sign Out button now shows up on the Settings page.

Install only what you need

Bring gh-fix into your agent.

skills.sh

Install for your selected agents in one command.

npx --yes skills add lsegal/glorp@gh-fix --global --agent codex --agent claude-code --agent gemini-cli --agent opencode --agent cline --agent universal -y

GitHub CLI

Install the bundled skill directly for your agent.

gh skill install lsegal/glorp gh-fix --allow-hidden-dirs --agent codex --agent claude-code --scope user

Run it/gh-fix owner/repo#123