Hire an AI software release readiness reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• Coverage gaps
• Documentation drift
• Rollout and rollback plan

How it does the job well

• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.
• Reproduce a bug before fixing it, and add a test that fails without the fix.
• Treat input from users, files and networks as untrusted. Validate it at the boundary.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: A code change is ready to ship and you want its tests, docs and rollout checked together.

• Coverage gaps. Missing, weak and stale tests, ranked by the behaviour at risk, from the Test coverage gap investigator.
• Documentation drift. Docs that no longer match the code, each tied to the change that broke it, from the Code and docs drift checker.
• Rollout and rollback plan. Preflight checks, rollout stages, health signals and rollback steps, from the Service rollout and rollback planner.
• Final summary. Source coverage, unresolved findings, missing facts and one next action.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Test coverage gap investigator. Share your repo or change. Get missing, weak and stale tests ranked by the behavior at risk. Hands the rollout step those gaps as known risks.
• Code and docs drift checker. Works from your code change and your docs. Get outdated docs and missing instructions traced to the changed behavior. Hands the rollout step the list of docs to fix.
• Service rollout and rollback planner. Share a release or infrastructure change. Uses the test gaps and stale docs from steps 1 and 2 as risks and tasks. Get preflight checks, rollout stages, health signals and a rollback plan.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id check-a-release-and-its-docs only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/check-a-release-and-its-docs/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your repo or the code change you plan to release (needed for steps 1 and 2)
• Your docs, such as README, setup guide, API docs and changelog
• Your release plan, with the target environment and any downtime limit (needed for step 3)

Functions and deliverables

• Software release readiness reviewer: Review missing tests and outdated docs, then plan release checks, rollout stages and a way to roll back.
  • Coverage gaps
  • Documentation drift
  • Rollout and rollback plan
• Software test gap finder: Share your repo or change. Get missing, weak and stale tests ranked by the behavior at risk.
  • A list of test gaps ranked from P0 (most serious) to P3.
  • For each gap, the code and test locations as path:line.
  • A specific test to add for each gap, with the scenario to check.
  • A short plan that says which tests to write first.
  • A list of checks that ran and checks that were skipped.
  Source: GitHub Copilot community.
• Code and documentation consistency checker: Share a feature or code change. Get outdated docs and missing instructions traced to the changed behavior.
  • A ranked list of stale or missing docs, from P0 to P3.
  • For each one, the code line and the doc line that disagree.
  • A plain fix direction for each finding.
  • A list of doc files most likely to need edits.
  • A note of what was checked and what was skipped.
  Source: GitHub Copilot community.
• Service rollout and rollback planner: Plan a safe service rollout and rollback. Share your release or infrastructure change and get preflight checks, stages, health signals and a rollback plan.
  • A summary with the risk level and rollback time
  • Preflight checks with a go or no-go list
  • Rollout steps with commands and a check after each
  • Health signals to watch over the first 15 minutes and beyond
  • A rollback plan with clear triggers
  • A communication plan and a list of contacts
  Source: GitHub Copilot community.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• A code change is ready to ship and you want its tests, docs and rollout checked together.
• You need a rollback plan before the first rollout stage.

Limits to check before starting

• You want a go or no-go verdict on your code and a list of blockers. Use the Code release readiness checker.
• You only need a read-only report on migrations, config, secrets and rollout order. Use the Release readiness reviewer.
• You only need the missing tests for one code change. Use the Code change test coverage reviewer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Add the complete skill pack to your AI.
• Share your goal and the files listed above.
• Ask it to follow the steps and mark any missing facts.
• Review the result before approving external actions.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/check-a-release-and-its-docs for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.