ironbee-verification

Category: Development & Coding | Uploader: ironbee-ai | Downloads: 0 | Version: v1.0（Latest）

MANDATORY browser verification after code changes. Activates when: implementing features, fixing bugs, modifying UI components, changing API endpoints, updating styles, refactoring code, or completing ANY task that changes application behavior. After writing or editing code files, you MUST verify changes through the browser-devtools MCP server and submit a verdict (pass or fail) before reporting task completion. If verification fails, submit the fail verdict before fixing. --- # IronBee Browser Verification ## Rule No task is complete until changes are verified in the browser — visually AND functionally. After verification, you MUST submit a verdict (pass or fail) before doing anything else. If verification fails, submit the fail verdict first, then fix. ## MCP Server Verification is performed using the **browser-devtools** MCP server (`browser-devtools-mcp` package). All browser interactions must go through this server's tools. ## Application Lifecycle

Changelog: Source: GitHub https://github.com/ironbee-ai/ironbee-cli

Directory Structure

Current level: src/clients/claude/

📁 hooks/
- 📄 clear-verdict.ts 2.5 KB
- 📄 require-verdict.ts 1.7 KB
- 📄 session-start.ts 3.0 KB
- 📄 track-action.ts 2.8 KB
- 📄 verify-gate.ts 1.7 KB
📄 index.ts 12.3 KB
📄 rule.md 2.8 KB
📄 skill.md 5.3 KB

SKILL.md

---
name: ironbee-verification
description: >
  MANDATORY browser verification after code changes. Activates when: implementing features,
  fixing bugs, modifying UI components, changing API endpoints, updating styles, refactoring code,
  or completing ANY task that changes application behavior. After writing or editing code files,
  you MUST verify changes through the browser-devtools MCP server and submit a verdict (pass or fail)
  before reporting task completion. If verification fails, submit the fail verdict before fixing.
---

# IronBee Browser Verification

## Rule
No task is complete until changes are verified in the browser — visually AND functionally. After verification, you MUST submit a verdict (pass or fail) before doing anything else. If verification fails, submit the fail verdict first, then fix.

## MCP Server
Verification is performed using the **browser-devtools** MCP server (`browser-devtools-mcp` package).
All browser interactions must go through this server's tools.

## Application Lifecycle
You are responsible for managing the application during verification:
- **Build** the application if needed (e.g. `npm run build`, `npm run dev`, `docker compose build`, or whatever the project uses)
- **Start** the dev server before navigating to any page (e.g. `npm run dev`, `docker compose up`, `docker compose up -d`)
- **Stop** the dev server after verification is complete (e.g. `Ctrl+C`, `docker compose down`)

If the application is already running, skip the start step. If the build fails, fix the build error before proceeding with verification.

## Flow
1. Implement your changes (write/edit code)
2. **Build and start** the application if not already running
3. **Functionally test** your changes through the browser:
   - **Navigate**: `mcp__browser-devtools__navigation_go-to` — go to the affected page(s)
   - **Interact**: Use the browser agent to **actually test** what you changed — click buttons, fill forms, submit data, trigger workflows, navigate between pages. Do not just look at the page.
   - **Screenshot**: `mcp__browser-devtools__content_take-screenshot` — capture the final visual state
   - **Accessibility**: `mcp__browser-devtools__a11y_take-aria-snapshot` — verify page structure
   - **Console**: `mcp__browser-devtools__o11y_get-console-messages` — check for errors
   Navigate, Screenshot, Accessibility, and Console tools are MANDATORY (the Stop hook checks the transcript for each one). Functional interaction is expected for every verification.
4. **Stop** the dev server when verification is complete
5. **IMMEDIATELY submit your verdict** — do NOT edit any code before submitting: `echo '<verdict-json>' | ironbee hook submit-verdict`
   - If everything works → submit pass verdict
   - If something is broken → submit fail verdict with issues describing what failed
   - **Never skip this step.** Every verification attempt must be recorded, pass or fail.
6. If you submitted a fail verdict → fix the code → rebuild → go back to step 2 → submit again → repeat until pass

## What good verification looks like
- Changed a form handler? → Start the app, fill the form, submit it, verify the response
- Added a button? → Click it, confirm the expected action happens
- Fixed a routing bug? → Navigate through the affected routes
- Updated an API call? → Trigger the action that calls the API, verify the result in the UI
- Changed styling? → Take a screenshot AND interact to ensure layout didn't break functionality

## How it works
- At session start, the SessionStart hook outputs your session ID
- After verification, submit your verdict: `echo '<verdict-json>' | ironbee hook submit-verdict`
- The submit-verdict command validates your verdict and records it
- When you stop, the Stop hook checks that browser tools were used AND a valid verdict exists
- If something is missing, the hook blocks you and gives you instructions

## Agent Teams
- Subagents focus on implementation only — do NOT verify
- The main orchestrator agent verifies ALL changes after subagents complete
- Each session's verification is isolated via session-specific verdict files

## Verdict format

On pass:
```json
{"session_id":"<your-session-id>","status":"pass","pages_tested":["http://localhost:3000/page"],"checks":["feature works"],"console_errors":0,"network_failures":0}
```

On fail (issues is required):
```json
{"session_id":"<your-session-id>","status":"fail","pages_tested":["http://localhost:3000/page"],"checks":["feature broken"],"console_errors":1,"network_failures":0,"issues":["button click handler not firing"]}
```

On pass after a previous fail (fixes is required):
```json
{"session_id":"<your-session-id>","status":"pass","pages_tested":["http://localhost:3000/page"],"checks":["feature works"],"console_errors":0,"network_failures":0,"fixes":["reattached click handler to submit button"]}
```

## Important
- **Always submit a verdict after every verification attempt** — both pass AND fail. Fail verdicts are tracked for analytics.
- The Stop hook checks BOTH that browser-devtools MCP tools were used AND a valid verdict exists
- Submit verdicts via `ironbee hook submit-verdict`, do NOT write verdict.json directly
- Every code edit (Write/Edit) automatically clears your session's verdict
- After 3 failed verification attempts, you may complete but must report issues

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

ironbee-verification

Directory Structure

SKILL.md

Report

Notice