# Enterprise Verify

> Evidence-based verification before any completion claim. No 'should work' or 'probably fine' — paste fresh test output or don't claim done. 7-check verification sequence. Use before committing or claiming work is complete.

- **Type:** Skill
- **Install:** `agentstack add skill-anotherben-claude-enterprise-skills-enterprise-verify`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [anotherben](https://agentstack.voostack.com/s/anotherben)
- **Installs:** 0
- **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [anotherben](https://github.com/anotherben)
- **Source:** https://github.com/anotherben/claude-enterprise-skills/tree/main/skills/enterprise-verify

## Install

```sh
agentstack add skill-anotherben-claude-enterprise-skills-enterprise-verify
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Enterprise Verify — Evidence-Based Completion Verification

## Why Evidence Matters

Without verification evidence, completion claims are beliefs — and beliefs ship bugs. "The code looks correct" means nothing when an import path is wrong, a test is silently skipped, or a debug `console.log` made it into the diff. Every check category below has caused a production incident at least once.

The distinction is simple: **evidence** is command output you can paste. **Belief** is anything else. This skill deals only in evidence.

---

## Step 1: Run verify.sh

The verification script runs all 7 checks mechanically and produces structured JSON evidence. Run it — don't run the checks manually.

```bash
bash .claude/skills/enterprise-verify/scripts/verify.sh \
  --base dev \
  --contract  \
  --output .claude/enterprise-state/-verification-evidence.json
```

**Flags:**
- `--base ` — base branch for diffs (default: `dev`)
- `--contract ` — contract file for postcondition extraction (optional)
- `--skip-build` — skip frontend build check (backend-only changes)
- `--output ` — where to write evidence JSON
- `--project ` — project root (auto-detected from cwd)

---

## Step 2: Read the JSON Evidence

The script outputs a JSON file with this structure:

```json
{
  "checks": {
    "test_suite":         { "result": "PASS|FAIL", "passed": N, "failed": N },
    "postcondition_trace": { "result": "MANUAL", "postconditions": "...", "test_names": "..." },
    "regression":          { "result": "PASS|FAIL", "new_failures": N },
    "build":               { "result": "PASS|FAIL|SKIP" },
    "diff":                { "result": "PASS", "files": [...] },
    "imports":             { "result": "PASS|FAIL", "unresolved": [...] },
    "debug_artifacts":     { "result": "PASS|FAIL", "findings": [...] }
  },
  "overall": "PASS|FAIL"
}
```

If `overall` is FAIL: stop, fix the failing checks, re-run verify.sh from scratch.

---

## Step 3: Complete the Two Manual Checks

The script automates 5 of 7 checks fully and collects data for the other 2. You must complete:

### Postcondition Trace (Check 2)
Map each postcondition from the contract to a specific test name from the `test_names` field. Use the EXACT test description from the runner output — not a paraphrase. If a postcondition has no matching test: FAIL.

### Diff Classification (Check 5)
The script lists changed files. Classify each as:
- **REQUIRED** — in the contract/plan
- **ENABLING** — needed to support a required change
- **DRIFT** — not related to this task → `git checkout -- path/to/file`

---

## Step 4: Write the Verification Report

```
===============================================
         ENTERPRISE VERIFICATION REPORT
===============================================

Task: [what was done]
Date: [YYYY-MM-DD]
Branch: [branch name]
Evidence: [path to JSON file]

## Automated Checks (from verify.sh)
  Check 1 — Test Suite:          [PASS — N passed, 0 failed]
  Check 3 — Regression Check:    [PASS — no regressions]
  Check 4 — Build Verification:  [PASS / SKIPPED (backend only)]
  Check 6 — Import Resolution:   [PASS — all imports resolve]
  Check 7 — Debug Artifacts:     [PASS — none found]

## Manual Checks
  Check 2 — Postcondition Trace: [PASS — N/N verified]
  Check 5 — Final Diff:          [PASS — N files, 0 drift]

  ────────────────────────────
  OVERALL: [PASS / FAIL]
```

---

## When to Run

| Trigger | Action |
|---------|--------|
| About to say "it's done" | Run verify.sh first |
| About to commit | Run verify.sh first |
| About to create a PR | Run verify.sh first |
| "One more thing" was fixed | Re-run verify.sh from scratch |

---

## Failure Recovery

When a check fails:
1. Fix the issue
2. Re-run verify.sh entirely (not just the failed check)
3. If tests fail after a fix: you introduced a regression — revert and try again

---

## Language That Signals Missing Evidence

If you catch yourself reaching for these phrases, you haven't run verification yet:

- "should work" / "probably fine" → run verify.sh, read the JSON
- "looks good" / "looks correct" → run verify.sh, report evidence
- "I'm confident" / "I believe" → confidence isn't evidence

---

## Edge Cases

**No formal contract?** Derive postconditions from the task description. Run verify.sh without `--contract` — it still runs all other checks.

**Only one file changed?** Still run verify.sh. A one-line change can break tests or leave debug artifacts.

**Test suite takes too long?** Run verify.sh once with full suite. Don't substitute partial runs.

See `references/verification-checks.md` for the detailed command reference behind each check.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [anotherben](https://github.com/anotherben)
- **Source:** [anotherben/claude-enterprise-skills](https://github.com/anotherben/claude-enterprise-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-anotherben-claude-enterprise-skills-enterprise-verify
- Seller: https://agentstack.voostack.com/s/anotherben
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.