CARBON — Engineering ConfidenceUser Guide
CHAPTER 40 / 60 Pro

/carbon-release-review

Independently synthesize code, evals, risk, production signals, severe failures, rollback readiness, evaluator independence, and uncertainty into a scoped AI release recommendation.

Jay · Your AI test managerProof & release confidence

When to use it

A release recommendation needs an independent challenge.

Before you start

Give the reviewer the underlying evidence, not only the optimistic summary. Check freshness, severity, evaluator independence and rollback readiness in a separate review context.

Try this in your coding agent.

/carbon-release-review Independently review checkout release evidence and unresolved risks.

Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →

ILLUSTRATIVE WALKTHROUGH

Independent release-evidence review

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Analyze
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing independent release-evidence review. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Independently review checkout release evidence and unresolved risks.

Show evidence

Here is the evidence trail to inspect: Compare source change, test record and original confidence narrative for contradictions.

Report

The reviewer asks for recovery evidence before approving the recommendation. Independence requires a separate review context in a real run.

CARBON

Example report

Illustration
Follow the cart state
Follow the cart state — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. Cart input
  2. Totals & state
  3. Checkout evidence

Illustrated outcome

The reviewer asks for recovery evidence before approving the recommendation.

Evidence to inspect

Compare source change, test record and original confidence narrative for contradictions.

Still untested / not established

Independence requires a separate review context in a real run.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For independent release-evidence review, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Compare source change, test record and original confidence narrative for contradictions. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Independence requires a separate review context in a real run.

The next decision

Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.

Adapt the example to your project

  1. Replace independent release-evidence review with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-release-review result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-release →/carbon-test →

Content checked against the local command definition: skills/carbon-release-review/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.