ironbee-verification

分类: 开发与编程 | 上传者: ironbee-ai | 下载: 0 | 版本: v1.0（最新）

代码更改后强制浏览器验证。在以下情况下激活：实现功能、修复错误、修改 UI 组件、更改 API 端点、更新样式、重构代码或完成任何更改应用程序行为的任务。编写或编辑代码文件后，您必须通过浏览器开发工具 MCP 服务器验证更改，并在报告任务完成之前提交结论（通过或失败）。如果验证失败，请提交失败判决后再修复。 --- # IronBee 浏览器验证 ## 规则在浏览器中对更改进行视觉和功能验证之前，任何任务都不算完成。验证后，您必须在执行其他操作之前提交判决（通过或失败）。如果验证失败，请先提交失败判定，然后修复。 ## MCP 服务器验证是使用 **browser-devtools** MCP 服务器（`browser-devtools-mcp` 包）执行的。所有浏览器交互都必须通过该服务器的工具。 ## 应用程序生命周期

更新日志: Source: GitHub https://github.com/ironbee-ai/ironbee-cli

目录结构

当前层级: tree/main/src/clients/claude/

📁 commands/
- 📄 ironbee-analyze.md 1.7 KB
- 📄 ironbee-verify.md 7.6 KB
📁 hooks/
- 📄 clear-verdict.ts 2.5 KB
- 📄 require-verdict.ts 1.7 KB
- 📄 require-verification.ts 3.0 KB
- 📄 session-start.ts 3.5 KB
- 📄 track-action.ts 4.9 KB
- 📄 verify-gate.ts 1.8 KB
📁 skills/
- 📄 ironbee-analyze.md 1.3 KB
📄 index.ts 14.6 KB
📄 rule.md 3.1 KB
📄 skill.md 5.7 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.

**Do NOT guess ports.** After starting the application, check the actual port (e.g. `docker compose ps`, process output, or config files) before navigating. Never assume a default port.

## Flow
1. Implement your changes (write/edit code)
2. **Build and start** the application if not already running
3. **Start verification**: `echo '{"session_id":"<your-session-id>"}' | ironbee hook verification-start`
   - This is REQUIRED before using any browser-devtools tools. Browser tools are blocked without it.
4. **Functionally test** your changes through the browser:
   - **Navigate**: `mcp__browser-devtools__bdt_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__bdt_content_take-screenshot` — capture the final visual state
   - **Accessibility**: `mcp__browser-devtools__bdt_a11y_take-aria-snapshot` — verify page structure
   - **Console**: `mcp__browser-devtools__bdt_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.
5. **Stop** the dev server when verification is complete
6. **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.
   - Submitting a verdict automatically ends the verification cycle.
7. 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

登录后下载/点赞/收藏 ❤ 5 | ★ 0

ironbee-verification

目录结构

SKILL.md

举报内容

提示