A documentation workflow for closing out a Quay bug fix. It creates updates for JIRA, release notes, the changelog, a pull request, and team communication.

Use it after fixing a Quay bug to record the root cause, changes, tests, affected versions, breaking changes, and required user action. It also prepares a changelog entry and pull request description.

It gathers the technical details of a fix into the documents needed for tracking, review, and release. It also separates user-facing explanations from internal engineering notes.

document — Skill for Claude Code by quay

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/quay/ai-helpers

agentmods

npx agentmods add skills/quay/ai-helpers/document

Made for: Claude Code.

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/quay/ai-helpers/document.svg)](https://agentmods.dev/skills/quay/ai-helpers/document)

Your own site

<a href="https://agentmods.dev/skills/quay/ai-helpers/document"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/document.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan B 1 finding. 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.00031	$0.00788
Opus 5	$0.00015	$0.00394
Sonnet 5	$0.00006	$0.00158
Haiku 4.5	$0.00003	$0.00079

Measured 2d ago against content hash 854d278965c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade B, and why

document scanned grade B with 1 finding 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 2d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/templates/pr-description.md 2>/dev/null

workflows/quay-bugfix/.claude/skills/document/SKILL.md · 119 lines

How it starts

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

Document Fix

Create all documentation artifacts needed to close out the bug fix.

Process

Step 1: Update JIRA Ticket

Create artifacts/quay-bugfix/docs/issue-update.md with:

Root cause summary
Description of the fix and what was changed
Links to commits, branches, or PRs
Test coverage added
Any breaking changes

Do NOT transition the JIRA ticket — automation handles state transitions.

Step 2: Create Release Notes Entry

Create artifacts/quay-bugfix/docs/release-notes.md with:

User-facing description of what was fixed
Impact and who was affected
Affected versions
Action required from users
Clear, non-technical language

Step 3: Update CHANGELOG

Create artifacts/quay-bugfix/docs/changelog-entry.md with:

Entry following project CHANGELOG conventions
Placed in Bug Fixes category
JIRA ticket reference included
Format: - Fixed [description] (PROJQUAY-XXXX)

Step 4: Create PR Description

Read the PR description template if available:

cat .claude/templates/pr-description.md 2>/dev/null

Create artifacts/quay-bugfix/docs/pr-description.md with:

Summary: What this PR does
Root Cause / Rationale: Why the change was needed
Changes: What changed (file references)
Test Plan: How to verify
JIRA Link: https://issues.redhat.com/browse/<TICKET>
Backport: Required or not (from assessment)

Step 5: Technical Communication

Create artifacts/quay-bugfix/docs/team-announcement.md with:

Message for engineering team
Severity and urgency of deployment
Testing guidance
Deployment considerations

Step 6: User Communication (if user-facing bug)

Create artifacts/quay-bugfix/docs/user-announcement.md with:

Customer-facing announcement
Non-technical explanation
Upgrade/mitigation instructions

Output

All files created in artifacts/quay-bugfix/docs/:

issue-update.md — JIRA comment text
release-notes.md — Release notes entry
changelog-entry.md — CHANGELOG addition
pr-description.md — Pull request description
team-announcement.md — Internal communication
user-announcement.md (optional) — Customer communication

Read the full file on GitHub · 119 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.

2d ago First seen · 119 lines · 31 tokens per session scan B 854d278965c4

Subscribe to this mod's changes

document is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 31 tokens to every session and 788 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Project management Writing and docs

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens

document