Guide · Agent skill
How to use the Release Review agent skill (release-review)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The release-review skill is a short set of instructions that tells an AI agent how to review Orchard deployment manifests, the configuration files that describe how software gets deployed. This guide explains what the skill changes in the agent's behaviour, how to install it, how to ask for a review, and where it has limits. After reading, you should be able to add the skill to your agent and run a review that points to specific files.
Release Reviewrohitg00/ai-engineering-from-scratch · MIT Download the skill Quick start
- 1Download the ZIP. Download the release-review ZIP from this page.
- 2Choose an install location. Use ~/.claude/skills/ for a personal install or the project's .claude/skills/ folder for a single project.
- 3Unzip the skill. Extract the ZIP into the chosen folder so the release-review files sit inside it.
- 4Or upload in the Claude apps. In the Claude apps, open Settings, go to Capabilities, then Skills, and upload the ZIP.
- 5Ask for a review. Send a plain request such as reviewing an Orchard deployment manifest, and include the file.
- 6Check the output. Confirm each finding lists its source path and that any missing evidence is reported.
What is an agent skill and what does release-review do?
An agent skill is a folder containing instructions that an AI agent reads when a task matches the skill's purpose. Instead of you writing the same instructions in every chat, the skill carries them.
The release-review skill is described as 'Review Orchard deployment manifests'. Its instructions are two rules: keep source paths in the result, and stop when evidence is missing. In practice, the agent should cite the file each finding comes from, so you can trace it back, and should report a gap rather than guess when the files do not contain what it needs.
- Keeps source file paths in its results so findings can be traced.
- Stops and reports when evidence is missing instead of guessing.
- Contains no executable scripts in the provided files.
Install the release-review skill
You can install the skill in two ways. For a personal setup, download the ZIP from this page and unzip it into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder instead.
If you use the Claude apps, you can upload the skill instead. Open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal install: unzip into ~/.claude/skills/.
- Project install: unzip into the project's .claude/skills/ folder.
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP.
How do you trigger the skill with a natural request?
The skill's description is 'Review Orchard deployment manifests', so ask for that task in plain language and include the manifest. Name the file or paste its contents, and say what you want checked.
Because the skill is specific to Orchard manifests, requests that mention Orchard deployment files are the clearest match. Requests about other deployment formats are less likely to use it.
- Review this Orchard deployment manifest and list any problems, with the file path for each.
- Check the Orchard deployment manifests in this folder and tell me what you cannot verify.
- Review the release manifests for this service and cite the source paths for every finding.
What to expect from a review
A review done with this skill should list each finding with the path of the file it came from. If the agent lacks the evidence to judge something, it should say so and stop on that point, not invent an answer.
Treat the output as a review aid. The skill gives the agent instructions only, so it can still miss problems.
- Each finding should name its source file path.
- Gaps in the evidence should be reported, not filled in with guesses.
- Use the output as input to a human review, not a final decision.
What does the skill need, and is it safe?
The source lists no requirements. The skill does not run scripts and does not use the network, according to the information provided. The files supplied are routing.json and SKILL.md; the SKILL.md text is the instruction set the agent follows.
Because the skill has no scripts, installing it does not run code on your machine. Still, the agent works with the files you give it, so review what you share before sending it.
- Requirements: none listed.
- Runs scripts: no.
- Uses network: no.
- Files included: routing.json and SKILL.md.
Tips for getting better reviews
Give the agent complete files rather than excerpts, since it can only cite paths it can see. Ask it to flag missing evidence explicitly so gaps are visible in the report.
If your team uses Orchard, a consistent review pass helps keep results comparable from one release to the next.
- Provide the full manifest and any files it refers to.
- Ask for source paths on every finding.
- Ask the agent to list what it could not verify.
What people use it for
- Reviewing an Orchard deployment manifest before a release and listing findings with file paths.
- Checking a set of release manifests in one project folder for consistent review notes.
- Producing a list of unverified items to hand to a release engineer.
- Giving a release team a traceable first-pass review to discuss in a sign-off meeting.
Frequently asked questions
How do I install the release-review skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for a personal install, or into a project's .claude/skills/ folder for one project. In the Claude apps, you can instead upload the ZIP under Settings, then Capabilities, then Skills.
Does release-review have any requirements?
The source lists no requirements. It runs no scripts and uses no network, according to the information provided.
Is the release-review skill free?
This page does not state a price or licence beyond the item being listed under MIT. Check the repository's licence file for the terms that apply.
What is an Orchard deployment manifest?
It is a configuration file describing how software gets deployed. The skill is built to review files in this format, so it adds little value for teams not using Orchard.
Can release-review replace a human release review?
No. The skill only gives the agent instructions, and the agent's review can still miss problems. It is suited to a first pass that a person checks before final sign-off.
Why does the agent say evidence is missing?
The skill tells the agent to stop and report when evidence is missing rather than guess. Supply the full files it refers to so it has the evidence it needs.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use release-review if you work with Orchard deployment manifests and want a consistent review pass where each finding points to a file path. Pick something else if you do not use Orchard, or if you need a final production sign-off, since this skill only guides the agent and cannot replace human review.
Download the skill