bubbles-evidence-capture

Capture verifiable execution evidence for Bubbles report sections and DoD items.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-evidence-capture-pkirsanov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bubbles-evidence-capture
Source: https://github.com/pkirsanov/bubbles/tree/main/skills/bubbles-evidence-capture
Command: npx skills add https://github.com/pkirsanov/bubbles --skill bubbles-evidence-capture-pkirsanov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents often claim work is done without proof, pasting fabricated or summarized test output. This Skill enforces a strict evidence standard so every claim in a Bubbles report.md or Definition-of-Done item is backed by real, captured command output that survives audits and lint checks. ## Core Features & Use Cases - Standardized evidence blocks: Records the exact command, exit code, and at least 10 lines of verbatim terminal output for every cited result. - Compact verifiable form for large output: Routes output over 40 lines through evidence-capture.sh, which emits a sha256 hash, line count, and a re-runnable --verify check. - Category-specific execution rules: Maps DoD claims (unit tests, API endpoints, database state, UI, builds, lint, coverage) to required live-execution actions and forbidden substitutes. - Use Case: When finishing a bug fix, you run the test suite through the capture script and paste the hashed evidence block into report.md, so the state-transition guard and artifact lint accept the DoD checkbox instead of rejecting it as fabrication. ## Quick Start Ask the agent to run the project's test command through the evidence-capture script and record the resulting evidence block in the report.md Test Evidence section.

Frequently Asked Questions about bubbles-evidence-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record test evidence that passes Bubbles DoD checks?▼

Run the actual test command and paste the exact command line, observed exit code, and at least 10 lines of verbatim output into the evidence block. Mark the result PASS or FAIL and never paste expected or summarized output.

How do I capture evidence when command output exceeds 40 lines?▼

Run the command through evidence-capture.sh with a label, which emits the exit code, line count, a sha256 hash of the full output, and the first and last 20 lines. Reviewers re-verify it with the --verify flag against the same command.

Why was my evidence block rejected by the artifact lint?▼

Common rejection causes include evidence under 10 lines, identical blocks reused across DoD items, missing command lines, summary-only output without test runner framing, or references to a prior session's terminal.

Can I cite code or config files instead of running commands as evidence?▼

No. Claims about tests, builds, lint, APIs, databases, or UI require live execution against the running stack. Reading source files, migrations, or configs is explicitly listed as a forbidden substitute.

How do I avoid PII scan failures when committing evidence?▼

Search captured output for real home paths like /home/<user>/ and replace every occurrence with the tilde form ~/<repo>/ before staging. The pii-scan.sh and gitleaks checks block commits containing absolute home paths.