onequery: Skill for Codex

.agents/skills/gh-pr-writing/SKILL.md

gh-pr-writing is a skill for Codex from wordbricks/onequery. It costs 57 tokens per session (575 once invoked), scanned A, original, Apache-2.0.

A GitHub pull-request writing guide that follows repository templates and local naming rules. It helps create or update titles and descriptions, including Conventional Commit-style titles such as `feat(web): ...`.

In plain words
What is it for?
Use it when creating or editing a pull request to inspect the changes, choose the title scope, fill the repository template, and record validation commands.
Why use it?
Pull requests can be rejected or misunderstood when their title, ticket marker, template, or validation details do not match project conventions.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is wordbricks/onequery's own configuration. It tells Codex how to work on onequery itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything onequery configures →

Reuse

Borrowing it

Nothing to install: this file belongs to wordbricks/onequery. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/wordbricks/onequery/main/.agents/skills/gh-pr-writing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/wordbricks/onequery

Made for: 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.

agentmods badge for gh-pr-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/wordbricks/onequery/gh-pr-writing/github.svg)](https://agentmods.dev/skills/wordbricks/onequery/gh-pr-writing)
Your own site
<a href="https://agentmods.dev/skills/wordbricks/onequery/gh-pr-writing"><img src="https://agentmods.dev/badge/skills/wordbricks/onequery/gh-pr-writing/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.

agentmods 80×15 button for gh-pr-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/wordbricks/onequery/gh-pr-writing"><img src="https://agentmods.dev/badge/skills/wordbricks/onequery/gh-pr-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 575 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00575
Opus 5.5 $0.00023 $0.00230
Sonnet 5.5 $0.00011 $0.00115
Haiku 4.5 $0.00006 $0.00057

Measured 5d ago against content hash 3ad7b1f688ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-01, from the pricing page.

Security

Grade A, and why

gh-pr-writing 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 5d 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.

.agents/skills/gh-pr-writing/SKILL.md · 63 lines

How it starts

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

GH PR Writing

Workflow

  1. Inspect changed files (git show --name-only --oneline HEAD or git diff --name-only).
  2. Choose title type and scope from the mapping below.
  3. Build title in Conventional Commit PR style.
  4. Run bun run format manually before commit/push to avoid push-time formatter diffs.
  5. Load PR template from .github/pull_request_template.md when present.
  6. Fill the template with concrete user-facing behavior, implementation details, and executed validation commands.
  7. Create or update the PR using gh pr create or gh pr edit.

Title Rules

  • Format: <type>(<scope>): <summary>.
  • Keep summary imperative and specific.
  • Do not omit scope unless scope is truly cross-cutting.
  • If user requires a ticket marker at the end, append exactly as requested (for example ... WOR-2610).

Type And Scope Mapping

See the following example:

  • feat(web): for user-visible frontend behavior in apps/dashboard, packages/ui, routing/UI/UX changes.
  • fix(web): for frontend bug fixes.
  • feat(server): for backend/API behavior changes in packages/server.
  • fix(server): for backend/API bug fixes.
  • feat(db): or fix(db): for schema/query/migration behavior in packages/db.
  • chore(repo): for tooling/config/lockfile/CI/repo maintenance.
  • refactor(<scope>): for structural code changes without behavior change.
  • test(<scope>): for test-only changes.
  • docs(<scope>): for documentation-only changes.
  • ...

When multiple scopes are touched, choose the dominant user impact scope.

PR Body Rules

  • Use the repository PR template verbatim section structure when it exists.
  • Prefer concrete, observable outcomes over abstract summaries.
  • Include exact command lines used for validation.
  • Explicitly note excluded items (for example: "README unchanged") when relevant.

Commands

# Inspect latest commit

git show --name-only --oneline HEAD

# Format before push

bun run format

# Create PR from template body file

gh pr create --base main --head <branch> --title "<title>" --body-file <body.md>

# Update title/body later

gh pr edit <pr-number-or-url> --title "<title>" --body-file <body.md>

Read the full file on GitHub · 63 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 5d ago First seen · 63 lines · 57 tokens per session scan A 3ad7b1f688ce

Subscribe to this mod's changes

gh-pr-writing is a skill published in the GitHub repository wordbricks/onequery (17 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 575 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-09-25.

Related

Other skills, from other repositories

officecli-pitch-deck

Use this skill when the user is building a fundraising / investor pitch deck — seed, Series A / B / C, convertible note, SAFE round, strategic raise. Trigger on: 'pitch deck', 'investor deck', 'Series A deck', 'Series B deck', 'Series C deck', 'fundraising deck', 'seed pitch', 'VC deck', 'raising capital', 'term sheet…

iOfficeAI/OfficeCLI · 163 tokens

morph-ppt

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style continuous motion, shapes that grow / move / rotate as the slide advances. Trigger on: 'morph', 'morph transition', 'smooth transition', 'continuous animation across slides', 'Keynote-style…

iOfficeAI/OfficeCLI · 169 tokens

officecli-academic-paper

Use this skill to build academic-style .docx output: journal / conference / thesis chapters carrying formal citation style (APA, Chicago, IEEE, MLA), numbered equations, figure & table cross-references, footnotes/endnotes, bibliography, or multi-column journal layout. Trigger on: 'research paper', 'journal paper'…

iOfficeAI/OfficeCLI · 141 tokens

officecli-financial-model

Use this skill when the user wants to build a financial model — 3-statement model, DCF valuation, LBO, SaaS unit economics, sensitivity / scenario analysis, debt schedule, or fundraising projections — in Excel. Trigger on: 'financial model', '3-statement model', 'P&L + BS + CF', 'DCF', 'WACC', 'NPV', 'terminal value'…

iOfficeAI/OfficeCLI · 222 tokens

officecli-pptx

Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with…

iOfficeAI/OfficeCLI · 106 tokens

officecli

Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the user wants to create, inspect, check formatting, find issues, add charts, or modify Office documents.

iOfficeAI/OfficeCLI · 56 tokens