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

/carbon-test

Test only a named feature, user flow, API, page, component, behavior, or change using CARBON Focused mode and optional named quality domains.

Richard · FormsStart & investigate

When to use it

You need a strict boundary around one feature or behavior.

Before you start

Name the feature, expected outcome and relevant quality concerns. Reject unrelated findings as a reason to silently broaden scope; keep them as follow-up candidates.

Try this in your coding agent.

/carbon-test Test password reset in src/auth, including expired reset links.

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

Password reset

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. 02Investigate
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing password reset. I’ll keep the scope and permissions explicit.

Investigate

Follow the weakest evidence link and record what remains blocked.

Show evidence

Here is the evidence trail to inspect: Synthetic expired token → submit → success message → old password still required.

Report

An expired reset link shows success but leaves the password unchanged. Real email delivery is excluded.

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

An expired reset link shows success but leaves the password unchanged.

Evidence to inspect

Synthetic expired token → submit → success message → old password still required.

Still untested / not established

Real email delivery is excluded.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For password reset, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Synthetic expired token → submit → success message → old password still required. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

Real email delivery is excluded.

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 password reset 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-test result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-generate →/carbon-more →

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