QA Release
jitpass/jit
Run jit's pre-release QA — a team of QA-engineer subagents (functionality, integrations, UX, bug-hunting, code review) that exercise a release candidate on this real Mac and hand back a consolidated…
Use before merging, shipping, publishing, or handing off work.
Install Release Readiness Review
$ npx skills add bbartling/open-fdd --skill release-readiness-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bbartling/open-fdd release-readiness-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bbartling/open-fdd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-readiness-review .claude/skills/release-readiness-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-readiness-review" agent skill from https://github.com/bbartling/open-fdd/tree/master/.agents/skills/release-readiness-review into .claude/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bbartling/open-fdd/tree/master/.agents/skills/release-readiness-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bbartling/open-fdd --skill release-readiness-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bbartling/open-fdd release-readiness-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bbartling/open-fdd.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-readiness-review .agents/skills/release-readiness-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-readiness-review" agent skill from https://github.com/bbartling/open-fdd/tree/master/.agents/skills/release-readiness-review into .agents/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bbartling/open-fdd --skill release-readiness-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bbartling/open-fdd release-readiness-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bbartling/open-fdd.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-readiness-review .cursor/skills/release-readiness-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-readiness-review" agent skill from https://github.com/bbartling/open-fdd/tree/master/.agents/skills/release-readiness-review into .cursor/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bbartling/open-fdd.git --path .agents/skills/release-readiness-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bbartling/open-fdd --skill release-readiness-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bbartling/open-fdd release-readiness-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bbartling/open-fdd.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-readiness-review .gemini/skills/release-readiness-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-readiness-review" agent skill from https://github.com/bbartling/open-fdd/tree/master/.agents/skills/release-readiness-review into .gemini/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bbartling/open-fdd release-readiness-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bbartling/open-fdd --skill release-readiness-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bbartling/open-fdd.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-readiness-review .github/skills/release-readiness-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-readiness-review" agent skill from https://github.com/bbartling/open-fdd/tree/master/.agents/skills/release-readiness-review into .github/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bbartling/open-fdd --skill release-readiness-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bbartling/open-fdd release-readiness-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bbartling/open-fdd.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-readiness-review .opencode/skills/release-readiness-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-readiness-review" agent skill from https://github.com/bbartling/open-fdd/tree/master/.agents/skills/release-readiness-review into .opencode/skills/release-readiness-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-readiness-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release-readiness-review- GitHub stars
- 173
- Token cost
- ~1.3k tokens
- SKILL.md length
- 557 words
- Files
- 3 (incl. references)
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Use before merging, shipping, publishing, or handing off work.
- Works in 5 steps: Objective: one sentence describing the… → Scope: files, folders, PR diff,… → Constraints: read-only vs write,… → …
- Tasks that involve Feature launches and release readiness
- SKILL.md covers Trigger, Non-goals, Operating principles and Subagent orchestration rules, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Release Readiness Review is an agent skill from bbartling/open-fdd. Use before merging, shipping, publishing, or handing off work. Runs subagents for verification, regression risk, operational readiness, docs, compatibility, and unresolved follow-ups.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/output-contracts.md` and `references/severity-rubric.md`).
It sits in Product & Project Management, covering Feature launches and release readiness and Subagents. The repository describes itself as: Fault Detection Diagnostics (FDD) for HVAC datasets.
When your agent uses it
- Tasks that involve Feature launches and release readiness
- Tasks that involve Subagents
Example prompts
- “/release-readiness-review”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Objective: one sentence describing the question to answer.
- Scope: files, folders, PR diff, services, packages, or docs to inspect.
- Constraints: read-only vs write, commands allowed, network/doc lookup allowed, and timeout.
- Required evidence: exact files/symbols/commands/sources to cite.
- Output schema: use the schema requested by the skill.
What it can do on your machine
Read from SKILL.md and the folder at commit e62b637. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Readiness Review loads about 1.3k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 557 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 557 words (~1,335 tokens).
“When the user asks if work is ready to merge/release/ship, prepare a release note, check readiness, or assess final risk after implementation.”
- name
- release-readiness-review
Files
SKILL.md and 2 other files (references) in .agents/skills/release-readiness-review of bbartling/open-fdd.
- SKILL.md
- references/output-contracts.md
- references/severity-rubric.md
Open the folder on GitHubat commit e62b637
Compare with similar skills
Release Readiness Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Readiness Review this skillbbartling/open-fdd | 173 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| QA Releasejitpass/jit | 161 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Personal Assistant Reviewedonyzpc/personal-assistant | 147 | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Utility Pm Skill Auditorproduct-on-purpose/pm-skills | 716 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Theboardroomdavepoon/buildwithclaude | 3.6k | — | ~1.5k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Personal Assistant Review
edonyzpc/personal-assistant
Review uncommitted or PR diffs in the personal-assistant Obsidian plugin with project-specific risk lanes, second-layer future-risk checks, severity discipline, subagent review routing, and…
Utility Pm Skill Auditor
product-on-purpose/pm-skills
Run a repo-wide cross-cutting governance audit via the pm-skill-auditor sub-agent.
Theboardroom
davepoon/buildwithclaude
Convene an AI executive board of directors (CEO, CFO, COO, CLO, CISO sub-agent personas) to vet a business idea, product concept, new service offering, M&A target, or operational initiative — and…
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
- Official
.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
More from bbartling/open-fdd
All 23 skills in this repoArchitecture Design Review
bbartling/open-fdd
A skill your agent uses to evaluate architecture, design proposals, refactors, module boundaries, dependency direction, data flow, concurrency model, and maintainability tradeoffs across any codebase.
Codebase Research Pass
bbartling/open-fdd
A skill your agent uses for structured research on an unfamiliar or complex codebase before planning, reviewing, or editing.
External Source Research
bbartling/open-fdd
A skill your agent uses when implementation or review depends on external documentation, standards, protocols, APIs, SDKs, changelogs, or version-specific behavior.
Multi Agent PR Review
bbartling/open-fdd
A skill your agent uses for rigorous pull request, branch, patch, or diff review.
Performance Ab Benchmark Review
bbartling/open-fdd
A skill your agent uses to design, run, or review performance work with reproducible A/B baselines.
Spec Contract Compliance Review
bbartling/open-fdd
A skill your agent uses to compare any codebase against a specification, API contract, protocol, policy, RFC, security baseline, or product requirements document.
Related
Categories
Questions about Release Readiness Review
What does Release Readiness Review do?
Use before merging, shipping, publishing, or handing off work. Release Readiness Review is an agent skill from bbartling/open-fdd. Use before merging, shipping, publishing, or handing off work.
When should I use Release Readiness Review?
Release Readiness Review fits situations like: tasks that involve Feature launches and release readiness; tasks that involve Subagents.
How do I install Release Readiness Review in Claude Code?
Run `npx skills add bbartling/open-fdd --skill release-readiness-review -a claude-code`. Or copy the skill folder (.agents/skills/release-readiness-review in bbartling/open-fdd) into .claude/skills/release-readiness-review in your project. Claude Code loads it when a task matches its description.
How do I install Release Readiness Review in Codex?
Run `npx skills add bbartling/open-fdd --skill release-readiness-review -a codex`. Or copy the skill folder (.agents/skills/release-readiness-review in bbartling/open-fdd) into .agents/skills/release-readiness-review in your project. Codex loads it when a task matches its description.
Can I use Release Readiness Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bbartling/open-fdd --skill release-readiness-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-readiness-review, .gemini/skills/release-readiness-review, .github/skills/release-readiness-review and .opencode/skills/release-readiness-review in your project.
What does Release Readiness Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Release Readiness Review is instructions for the agent only.
Does Release Readiness Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Readiness Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Release Readiness Review use?
Release Readiness Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Release Readiness Review use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 473 tokens, read only when the agent opens those files.
What are the alternatives to Release Readiness Review?
Skills that share tags, products or a category with Release Readiness Review: QA Release (jitpass/jit, 161 stars), Personal Assistant Review (edonyzpc/personal-assistant, 147 stars), Utility Pm Skill Auditor (product-on-purpose/pm-skills, 716 stars) and Theboardroom (davepoon/buildwithclaude, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Readiness Review?
bbartling (a GitHub user) maintains it in bbartling/open-fdd, which has 173 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 9, 2026.
Source: bbartling/open-fdd on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.