Skip to content
Skills Library
Programming · Automation

appraise-github-issues

/appraise-github-issues

Appraise a GitHub issue backlog unattended: for each issue, decide whether it is still real and how big it is, then apply the answer to the tracker as a size label, a needs-decision or needs-human label with the question stated, or a close carrying a re-checkable receipt. A close is confirmed by a second engine before it is made. Runs once, on one issue, over the whole backlog, or as a periodic heartbeat, and is the sizing stage of burn-down-github-issues. Use when the task is "size the backlog", "appraise every issue in this repo", "close what is already done", "triage recent issues without f

Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 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.
Content35 / 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
9
Scripts
4
HTML comments
0
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
  • 4 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: appraise.ts, lib/appraise.test.ts, lib/appraise.ts, lib/callbacks.ts

What it does and when to use it

Appraise a GitHub issue backlog unattended: for each issue, decide whether it is still real and how big it is, then apply the answer to the tracker as a size label, a needs-decision or needs-human label with the question stated, or a close carrying a re-checkable receipt. A close is confirmed by a second engine before it is made. Runs once, on one issue, over the whole backlog, or as a periodic heartbeat, and is the sizing stage of burn-down-github-issues. Use when the task is "size the backlog", "appraise every issue in this repo", "close what is already done", "triage recent issues without f

Triggers from the description

size the backlogappraise every issue in this repoclose what is already done
Original author description

Appraise a GitHub issue backlog unattended: for each issue, decide whether it is still real and how big it is, then apply the answer to the tracker as a size label, a needs-decision or needs-human label with the question stated, or a close carrying a re-checkable receipt. A close is confirmed by a second engine before it is made. Runs once, on one issue, over the whole backlog, or as a periodic heartbeat, and is the sizing stage of burn-down-github-issues. Use when the task is "size the backlog", "appraise every issue in this repo", "close what is already done", "triage recent issues without f

How it works

  1. The second opinion on a close
  2. What happens after a size is not the appraiser's to say
  3. Run it
  4. Read next
  5. Standards this skill enforces
  6. Hard dependencies
  7. The ceiling, named
Original SKILL.md headings · 100 lines, 972 words
SKILL.md preview
---
name: appraise-github-issues
description: >-
  Appraise a GitHub issue backlog unattended: for each issue, decide whether it is still real and
  how big it is, then apply the answer to the tracker as a size label, a needs-decision or
  needs-human label with the question stated, or a close carrying a re-checkable receipt. A close
  is confirmed by a second engine before it is made. Runs once, on one issue, over the whole
  backlog, or as a periodic heartbeat, and is the sizing stage of burn-down-github-issues. Use when
  the task is "size the backlog", "appraise every issue in this repo", "close what is already
  done", "triage recent issues without fixing them", or "keep the backlog sized". Requires a
  per-repository config (its own, or the burndown's) and the codex and claude CLIs for the default
  seats. Skip for fixing anything; this skill never writes to the repository.
---

# Appraise GitHub Issues

One read-only agent turn per issue answers two questions and stops: is it still real, and how big
is it. The answer lands on the issue, and that is the whole contract. Nothing reads this process;
the burndown, a person, or another skill reads the tracker.

This feature is about an **issue**; its children are **appraisals**: one verdict about one issue,
judged against the fetched base ref at one moment.

| Verdict | What lands on the issue |
|---|---|
| `valid` | a `size: N` label on the configured scale; a comment when it disagrees with a size already there |
| `already-fixed`, `obsolete` | a close with a receipt a stranger can re-check, after a second engine agrees |
| `needs-decision` | the label, and the exact question a person must answer |
| `needs-human` | the label, and what access or authority an agent lacks |

## The second opinion on a close

A close is the one appraisal verdict that is a write with consequences: a wrongly kept issue costs
a re-read, a wrongly closed one disappears. So before an issue closes, a **confirmer** on another
engine, with none of the appraiser's context, re-checks the receipt against the base ref: the
commit is an ancestor and does what was asked, or the file as the base holds it no longer has the
premise. Agreement closes the issue with both receipts on the thread. Disagreement labels it
`needs-human` with both opinions, and a person breaks the tie. A confirmer that crashes or writes
nothing is not evidence either way; the close is not made and the issue stays unsized.

Sizing and hand-offs stay single-opinion. They are labels a person can change.

## What happens after a size is not the appraiser's to say

A producer puts files named `on-size-<N>`, `on-size-over-<M>`, or `on-size` into a callbacks
directory, and the appraiser looks one up for the points it just applied and runs it: an
executable with the appraisal as JSON on stdin, a `.md` prompt as one agent turn on the callback
seat (a seat is a role an agent fills; this one runs callback prompts), or both. The burndown
writes the callbacks it ships there on every start, and that is how `carve-github-issue`, which
breaks an oversized issue into smaller ones, is reached without the appraiser knowing it exists. The ladder, the two forms, and the payload are in `references/callbacks.md`.

Keep the appraiser and the confirmer on different engines; the driver refuses to start when they
match. `--no-confirm` (or `confirmCloses: false`) closes on the appraiser alone, for a tracker whose
authors you trust to that degree, and then the confirmer's engine does not matter.

## Run it

From inside the target repository:

```bash
bun run <this-skill-dir>/appraise.ts --dry-run             # select and print; no lock, no agent, no GitHub write (only runs/appraise.log)
bun run <this-skill-dir>/appraise.ts --limit 12            # up to 12 unsized issues in the window
bun run <this-skill-dir>/appraise.ts --age-days 90         # widen the window to 90 days for this run
bun run <this-skill-dir>/appraise.ts --issue <n>           # one issue, whatever its age or size
bun run <this-skill-dir>/appraise.ts --all                 # the whole open backlog, not only the window
bun run <this-skill-dir>/appraise.ts --all --include-sized # re-judge everything, sized or not
bun run <this-skill-dir>/appraise.ts --every <minutes>     # heartbeat: appraise whatever is new, on a cadence you choose
bun run <this-skill-dir>/appraise.ts --appraiser codex:gpt-5.6-sol --confirmer claude:claude-opus-5
bun run <this-skill-dir>/appraise.ts --callbacks <dir>     # where a producer's size callbacks live; --callback-seat engine[:model]
```

`<this-skill-dir>` is the filesystem path of this directory wherever the collection is checked out;
it is a path, not a skill name. The command reads `appraise-github-issues.config.ts` at the
repository root, or the burndown's `burn-down-github-issues.config.ts` when that is what the
repository has (`references/adopting.md`). Every run is teed to `<worktreeRoot>/runs/appraise.log`.

## Read next

| Need | Read |
|------|------|
| Adopt it in a repository: the config, what it writes to the tracker, first-run order, boundaries | `references/adopting.md` |
| Extend it: the size-callback ladder, the executable and prompt forms, the payload, what a prompt may report | `references/callbacks.md` |

## Standards this skill enforces

- **Read-only.** The appraiser and the confirmer edit no file, create no branch, install nothing,
  and run no suite. Their working directory is an empty scratch directory, not a checkout.
- **The base ref is the evidence.** "Already in the base" is judged against the fetched base
  branch, never the main checkout's working state.
- **A decision beats a small diff.** An issue that turns on a product or domain ruling nobody has
  made is `needs-decision`, however small the change.
- **The written convention beats the issue's prescription.** When an issue prescribes a remedy the
  repository's convention docs rule out, the appraiser sizes the convention-respecting remedy and
  says so; it does not stop for a human.
- **Closes carry receipts, and receipts get re-checked.** Narrative alone never closes an issue.

## Hard dependencies

- The sibling `fix-github-issue` skill, imported for the agent runner, config loader, prompt
  renderer, and label helpers. It ships in the same collection.
- `gh` authenticated with issue-edit rights on the target repository.
- The CLIs the seats name (by default `codex` and `claude`) on `PATH`.

## The ceiling, named

The appraiser executes the tracker's claims against the code, not your intent: an issue that is
internally coherent and wrong is sized competently. Issue bodies and comments are an untrusted
instruction channel read by agents with their approval gates bypassed; the read-only contract is a
prompt, not a sandbox, so run this only on trackers whose authors you trust as far as the
credentials the agents hold. The confirmer's independence is model-level, not identity-level; it
runs as the same GitHub account. And a size is a judgement on the configured scale, not a
measurement; disagreements between runs are recorded on the issue, not resolved by it.
Files in this package (9)
  • SKILL.md 7 KB
  • appraise.ts 13 KB
  • lib/appraise.test.ts 2 KB
  • lib/appraise.ts 29 KB
  • lib/callbacks.ts 5 KB
  • prompts/appraise.md 6 KB
  • prompts/confirm-close.md 3 KB
  • references/adopting.md 4 KB
  • references/callbacks.md 3 KB

Versions

The database has no other skills named appraise-github-issues.

Database snapshot: 13.11.2026 · package version c0335b295251 (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

  • 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…
  • 100manage-issues
    Create, edit, search, close, and triage GitHub Issues via the gh CLI. Use when asked to file a bug, request a feature, create a task, report a problem, search the backlog, triage issues, or manage the issue tracker. Also use when the user says 'create an issue', 'file a bug',…
  • 100github-backlog-triage
    Use when the user invokes backlog triage for a GitHub repo''s open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
  • 100triage
    Triage and size tracker issues — give every open issue a verdict (OK, STALE, SUPERSEDED, DUP, BLOCKED, HUMAN, BOT), close the ones that are no longer real only on evidence from the code on main, and apply exactly one size/S|M|L|XL label measured as "the weakest model that can…
  • 90issues
    把项目待办与记忆放进 GitHub issues。来自审读、审计或用户的每条审查发现都可归档为独立 issue 并避免重复;列出与当前工作相关的未关闭 issue;关闭时用评论记录原问题、尝试过的方法、有效方案和最终修复。当审查发现或问题需要跟踪时(论文误导性断言、代码 bug、日后改进),在开工/续接并决定下一步时,或修复落地后需要带记录关闭 issue 时使用。需要 GitHub CLI;发布到公开仓库前会警告。用户说 "file issues"、"list issues"、"close issue"、"归档审查发现" 或 "列出待办 issue" 时也使用。
  • 100maintainer-triage
    Triages the open issues of a GitHub repo. Reads them with gh, sorts each into bug, feature, question, duplicate, needs-repro or stale, finds likely duplicates, and drafts labels plus a short, human reply for every issue. Writes a triage report first and only applies labels,…

Feedback and reports

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