Skip to content
Skills Library
Programming · Review & audit

prove-github-issue

/prove-github-issue

The Proving lane of the fix pipeline: one headless agent turn, on a fresh context, that proves a commit a coder pushed for a GitHub issue and hands it to review as a ready pull request carrying that proof, per `prove-work-on-github`. It changes no code and pushes nothing to the branch; a change it cannot prove goes back to the coder with what is missing. Run by `fix-github-issue` (and so by `burn-down-github-issues`) after every push it announces, after a reviewer asks for more evidence, and after the base moves beneath an existing proof. Skip it for writing the change or for judging someone e

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
1
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Scripts: lib/prove.ts

What it does and when to use it

The Proving lane of the fix pipeline: one headless agent turn, on a fresh context, that proves a commit a coder pushed for a GitHub issue and hands it to review as a ready pull request carrying that proof, per `prove-work-on-github`. It changes no code and pushes nothing to the branch; a change it cannot prove goes back to the coder with what is missing. Run by `fix-github-issue` (and so by `burn-down-github-issues`) after every push it announces, after a reviewer asks for more evidence, and after the base moves beneath an existing proof. Skip it for writing the change or for judging someone e

Original author description

The Proving lane of the fix pipeline: one headless agent turn, on a fresh context, that proves a commit a coder pushed for a GitHub issue and hands it to review as a ready pull request carrying that proof, per `prove-work-on-github`. It changes no code and pushes nothing to the branch; a change it cannot prove goes back to the coder with what is missing. Run by `fix-github-issue` (and so by `burn-down-github-issues`) after every push it announces, after a reviewer asks for more evidence, and after the base moves beneath an existing proof. Skip it for writing the change or for judging someone e

How it works

  1. What a prover is told, and what it is not
  2. How the driver checks the answer
  3. Hard dependencies
  4. The ceiling, named
Original SKILL.md headings · 49 lines, 501 words
SKILL.md preview
---
name: prove-github-issue
description: >-
  The Proving lane of the fix pipeline: one headless agent turn, on a fresh context, that proves a
  commit a coder pushed for a GitHub issue and hands it to review as a ready pull request carrying
  that proof, per `prove-work-on-github`. It changes no code and pushes nothing to the branch; a
  change it cannot prove goes back to the coder with what is missing. Run by `fix-github-issue`
  (and so by `burn-down-github-issues`) after every push it announces, after a reviewer asks for
  more evidence, and after the base moves beneath an existing proof. Skip it for writing the change
  or for judging someone else's proof.
---

# Prove GitHub Issue

One seat, one lane: Proving (D2). The prover's turn ends at a **ready pull request whose head is the
proven commit**. It starts from durable state alone (the issue, the pushed branch, and the coder's
announcement on the thread), so it never inherits a coder's long transcript, and a prover that is
killed costs only the proof: the coded commit stands, and the next attempt proves it again rather
than coding it again.

This feature is about a **proof**; its children are **receipts**: artifacts pinned to commits the
remote holds, each covering one thing the change claims.

| Verdict | What it means | What happens next |
|---|---|---|
| `proved` | a ready pull request, `pr`, whose head is `sha`, the lane's head | the card goes to review |
| `unprovable` | the change does not do what the issue asks, or what it claims cannot be shown; `brief` says what | the driver announces it (`<!-- loop-step unproved ... -->`), spends an attempt, and a coder fixes it on the same branch |
| `needs-decision`, `needs-human` | proof needs a ruling, or access an agent lacks | the issue is held with the question stated |
| `failed` | anything else | the attempt is counted; the coded commit stands |

## What a prover is told, and what it is not

The prompt is `prompts/prove.md`. Its brief is the coder's hand-off on a first proof, the
reviewer's points when a review asked for more evidence, or the catch-up that moved the base
beneath an existing proof. It loads `prove-work-on-github` for the definition of proof.

The prover reruns the repository's gate only when the head it proves differs from the commit the
coder gated (the driver merged the base in at the seam); otherwise the coder's gate stands and CI is
the second opinion. Like the coder, it never chases the base itself.

## How the driver checks the answer

`lib/prove.ts` exports `runProve(ctx, issue, cwd, coded, brief)`. It runs the seat and returns its
answer, or `failed` when the answer cannot be believed: a crash, a kill at the cap, an unknown
verdict, a `proved` that names no pull request or is pinned to a head other than the lane's, or an
`unprovable` that tells the coder nothing to fix. The control file is `loop-proof.json`.

## Hard dependencies

- The sibling `fix-github-issue` skill, imported for the agent runner, the context, the prompt
  renderer, and the Work markers. It ships in the same collection and is what runs this seat.
- The sibling `prove-work-on-github` skill, which the prover loads.
- `gh` authenticated with pull-request rights, and the CLI the `worker` seat names, on `PATH`.

## The ceiling, named

A proof is evidence an independent reviewer can re-check, not a verdict; the reviewer, on another
engine, still decides whether it is enough. The prover runs on the same engine as the coder by
default: a fresh context stops proof-by-memory, and engine independence is the reviewer's job.
Files in this package (3)
  • SKILL.md 3 KB
  • lib/prove.ts 6 KB
  • prompts/prove.md 5 KB

Versions

The database has no other skills named prove-github-issue.

Database snapshot: 13.11.2026 · package version 079ba9e3be7f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100fix-github-issue
    Turn one known GitHub issue into a merged pull request, headless: a coder and then a prover in the issue's own git worktree, a pull request carrying the proof, an isolated second-engine reviewer, and a serial pull master that checks import-closure staleness against the base…
  • 87burn-down-github-issues
    Run an unattended burndown of a GitHub issue backlog as cards on a per-operator GitHub Projects board whose lanes are an explicit state machine: appraise and size the inbox, carve what is over the ceiling, fix the ready ones in parallel git worktrees, prove each fix on a draft…
  • 100dev-issue
    Implements GitHub issues end-to-end. Use to turn an issue into a merge-ready PR.
  • 90gh-issue-fix-flow
    End-to-end GitHub issue fix workflow using gh, local code changes, builds/tests, and git push. Use when asked to take an issue number, inspect the issue via gh, implement a fix, run XcodeBuildMCP builds/tests, commit with a closing message, and push.
  • 100show-your-work
    Use when the user asks to prove, verify or QA a change, commit or pull request in the running app (web, API, or a target you define), wants evidence a person can check that it works before merging, says "prove my changes", "show it works" or "proof of work", asks to prove bugs…
  • 91github-pr-audit
    Use when auditing a GitHub PR or issue before merge.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.