CARBON — Engineering ConfidenceUser Guide
CHAPTER 51 / 60 Pro

/carbon-full-report

Show CARBON's complete evidence-qualified quality record in one dark, visual report: every known test case, declared automation and frameworks, durable execution history and trends, findings, and human decision context.

Jay · Your AI test managerTesting operations

When to use it

You need the complete retained quality record in one place.

Before you start

Open saved findings, tests, automation and human context. Check revision and timestamps before interpreting old evidence. This command displays the record; it does not rerun every check.

Try this in your coding agent.

/carbon-full-report Show the complete saved quality report for the latest checkout assessment.

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

Saved checkout quality record

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 saved checkout quality record. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Show the complete saved quality report for the latest checkout assessment.

Show evidence

Here is the evidence trail to inspect: Source revision + journey results + reproducible defect + untested browsers.

Report

Findings, evidence and blocked checks are collected in one report. This command presents saved evidence rather than rerunning every check.

CARBON

Example report

Illustration
Project → decisions → retained evidence
Project → decisions → retained evidence — TestBucks teaching screen

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

  1. TestBucks project
  2. Command action
  3. Reviewable output

Illustrated outcome

Findings, evidence and blocked checks are collected in one report.

Evidence to inspect

Source revision + journey results + reproducible defect + untested browsers.

Still untested / not established

This command presents saved evidence rather than rerunning every check.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For saved checkout quality record, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Source revision + journey results + reproducible defect + untested browsers. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

This command presents saved evidence rather than rerunning every check.

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 saved checkout quality record 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-full-report result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-more →/carbon-confidence →

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