CARBON — Engineering ConfidenceUser Guide
CHAPTER 56 / 60 Core + Pro

/carbon-background

Set up, pause, inspect or review Jay's bounded background checks after code changes.

Jay · Your AI test managerTesting operations

When to use it

You want opt-in checks while working between changes.

Before you start

Verify supported trusted host hooks, explicit project consent and saved limits. Keep pause/kill-switch controls available. Unsupported hosts should offer an explicit bounded run—not a hidden daemon.

Try this in your coding agent.

/carbon-background Show a proposed background-check scope for src/auth; wait for my consent to enable it.

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

Proposed auth background checks

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 proposed auth background checks. I’ll keep the scope and permissions explicit.

Analyze

Analyze: Show a proposed background-check scope for src/auth; wait for my consent to enable it.

Show evidence

Here is the evidence trail to inspect: Choose local checks, trigger, limits and pause control; show proposed configuration.

Report

Jay presents the scope and waits for consent to enable it. Nothing is enabled by this demo or by merely viewing a proposal.

CARBON

Example report

Illustration
Inspect the identity boundary
Inspect the identity boundary — TestBucks teaching screen

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

  1. User action
  2. Identity / validation
  3. Allowed outcome

Illustrated outcome

Jay presents the scope and waits for consent to enable it.

Evidence to inspect

Choose local checks, trigger, limits and pause control; show proposed configuration.

Still untested / not established

Nothing is enabled by this demo or by merely viewing a proposal.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For proposed auth background checks, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Choose local checks, trigger, limits and pause control; show proposed configuration. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Nothing is enabled by this demo or by merely viewing a proposal.

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 proposed auth background checks 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-background result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-settings →/carbon-auto →

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