What is q-setup-approve?

A skill that creates a project-specific /approve command for checking and merging approved pull requests, which are proposed code changes submitted for review.

Configuring and generating an /approve workflow that verifies required checks and review conditions before merging, with optional post-merge actions.

It first gathers the project's source-control, continuous-integration, and pull-request rules so approval follows the team's actual process.

q-setup-approve — Skill for Claude Code and Codex by jlong/quiddity

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 jlong/quiddity --skill q-setup-approve

Clone the repo

git clone --depth 1 https://github.com/jlong/quiddity

Made for: Claude Code, Codex.

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/jlong/quiddity/q-setup-approve/github.svg)](https://agentmods.dev/skills/jlong/quiddity/q-setup-approve)

Your own site

<a href="https://agentmods.dev/skills/jlong/quiddity/q-setup-approve"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-approve/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/jlong/quiddity/q-setup-approve"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-approve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 597 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.00050	$0.00597
Opus 5.5	$0.00020	$0.00239
Sonnet 5.5	$0.00010	$0.00119
Haiku 4.5	$0.00005	$0.00060

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

Security

Grade A, and why

q-setup-approve 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/q-setup-approve/SKILL.md · 68 lines

How it starts

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

Setup /approve

You are generating a custom /approve skill for the user's project.

Required categories

This skill needs the following tools.json categories: source-control, ci, pr

Process

Ensure tools are configured. Check if .quiddity/tools.json exists and contains the source-control, ci, and pr categories. For any missing categories, run /q-which-tools with those categories (e.g., /q-which-tools source-control ci pr).
Read the configuration. Load all available Quiddity context:
- .quiddity/project.md — project structure, CI/CD configuration
- .quiddity/process.md — merge strategy, review requirements, post-merge workflow
- .quiddity/tools.json — extract the source-control, ci, and pr categories
Ask skill-specific questions not covered by tools.json:
- Should the skill accept a PR number as an argument? (e.g., /approve 123) Or default to the current branch's PR?
- What should happen after merge? (update issue status, notify, etc.)
- Should it verify that all review comments are resolved?
- Any post-merge cleanup steps? (delete local branch, pull latest, etc.)
Generate the skill. Write a complete /approve SKILL.md to the project's skills directory. The generated skill should:
- Accept an optional PR number argument (defaulting to current branch's PR)
- Verify all CI checks pass
- Verify no unresolved review comments (if configured)
- Verify required approvals are met
- Perform the merge using the configured strategy (squash, merge, rebase)
- Update the linked issue status (e.g., move to "Done" or "Shipped")
- Clean up the branch if configured
- Report clearly if anything blocks the merge
- Reference .quiddity/tools.json for all tool-specific configuration
Show the generated skill to the user and ask for confirmation before finalizing.

Generated skill template

The generated /approve skill should follow this general structure, adapted to the user's specific tools:

Read the full file on GitHub · 68 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 · 68 lines · 50 tokens per session scan A 4ccd9681ff70

Subscribe to this mod's changes

q-setup-approve is a skill published in the GitHub repository jlong/quiddity (5 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 597 once invoked, about $0.0002 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.

Code review Git and workflow

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens