A pre-merge or pre-deployment review that lists code changes and asks the user questions about them. A merge is the act of combining changes into a shared code branch; deployment publishes them for use.

Use it to create a change report, describe behavior changes, record risks and decisions, and test the user's understanding with a quiz.

It helps catch misunderstandings and production risks after a long coding session, before changes are merged or released.

merge-quiz — Skill for Claude Code by orenluxy/fable-method

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add orenluxy/fable-method --skill merge-quiz

Clone the repo

git clone --depth 1 https://github.com/orenluxy/fable-method

Made for: Claude Code.

Or install fable-method, the plugin that ships this one along with the rest of its 8 skills, 2 agents, 1 hook, 1 plugin.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/orenluxy/fable-method/merge-quiz/github.svg)](https://agentmods.dev/skills/orenluxy/fable-method/merge-quiz)

Your own site

<a href="https://agentmods.dev/skills/orenluxy/fable-method/merge-quiz"><img src="https://agentmods.dev/badge/skills/orenluxy/fable-method/merge-quiz/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/orenluxy/fable-method/merge-quiz"><img src="https://agentmods.dev/badge/skills/orenluxy/fable-method/merge-quiz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 661 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.00661
Opus 5.5	$0.00031	$0.00264
Sonnet 5.5	$0.00016	$0.00132
Haiku 4.5	$0.00008	$0.00066

Measured 2mo ago against content hash 5786528b52ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

merge-quiz scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/merge-quiz/SKILL.md · 39 lines

How it starts

The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Merge Quiz

Purpose: after a long session, the user's mental model of the changes is a map that has drifted from the territory. Merging on a drifted map is how production incidents happen. The quiz forces the map to be re-synced before the merge button exists.

Procedure

Generate the change report as a single self-contained HTML file. If subagents are available, delegate the mechanical inventory (diff stats, file list, test run, notes import) to the report-builder agent (sonnet) and build the report from its skeleton — the risk register and the quiz remain yours. If an external stoploss tool is on PATH, run its report and include the numbers. Report sections:
- Summary: what was built, in 5 lines max.
- Change inventory: every file touched, grouped by subsystem, with one line per file on what changed and why.
- Behavior changes: what a user/consumer of this system will experience differently. This section matters more than the file list.
- Risk register: the 3 changes most likely to break something, and how to verify each.
- Decisions & Deviations: imported from IMPLEMENTATION_NOTES.md if it exists.
Append the quiz at the bottom of the report: 5–8 questions testing whether the user actually understands the changes. Mix of:
- "What happens now when X?" (behavior)
- "Why was Y chosen over Z?" (decisions)
- "Which file would you edit to change W?" (territory knowledge)
- At least one question about a deviation, if any exist. Questions must be answerable only by someone who understands the changes — not by pattern-matching the report's summary.
Grade strictly. The user answers in chat. A wrong or fuzzy answer means: explain the correct answer with a pointer to the relevant code, then re-ask a variant. Do not proceed to merge steps until all answers are solid.
Only after a clean pass: provide the merge/deploy commands or perform them if asked.

Calibration

Session touched < ~50 lines in familiar territory: skip the quiz, offer a 3-line summary instead. The gate exists for long sessions, not for typo fixes. Say explicitly that you're skipping it and why.
Production systems (databases, payment, live servers): the quiz is mandatory regardless of size, and the risk register must include a rollback plan.

Read the full file on GitHub · 39 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 39 lines · 78 tokens per session scan A 5786528b52ab

Subscribe to this mod's changes

merge-quiz is a skill published in the GitHub repository orenluxy/fable-method (2 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 661 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Code review Git and workflow ai-agents anthropic claude-ai claude-code-plugin developer-tools

merge-quiz next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
merge-quizorenluxy/fable-method	Skill	2	1mo ago	MIT	A	78	Claude Code
OCR Review-to-Approval Loopspencermarx/open-code-review	Skill	382	5d ago	Apache-2.0	A	213	Claude Code
pre-release-reviewgtapps/hermitd	Skill	84	yesterday	MIT	A	188	Codex
github-pr-creationfvadicamo/dev-agent-skills	Skill	72	1mo ago	MIT	A	75	Claude Code
stack-prHigorAlves/orc	Skill	7	yesterday	MIT	A	52	Claude Code, Codex
upstreamNexaDuo/mARC	Skill	7	14d ago	MIT	A	83	Claude Code, Codex
inline-reviewHigorAlves/orc	Skill	7	yesterday	MIT	A	43	Claude Code, Codex