agentleFS
Sign inStart free
timeyourtimeyour/agentskills-audit-collection/.cursor/rules/audit-live-workbench.mdc

agentskills-audit-collection / rules

Cursor rule1 starsChanged 6 months agoMITView on GitHub

Live Audit Workbench — sync run-state.json while running /audit

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository11 other files it gives its agents.

The file

We split this audit-live-workbench.mdc into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user runs /audit, a website audit, or 交付验收:

    line 8
  2. Very specific:

    Update every stage: write validation/artifacts/<runId>/run-state.json per live-run-protocol.md (activeAnnotation, step in_progress / …

    line 11
  3. Very specific:

    Finish: write audit-report.json in the run folder.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
audit-live-workbench.mdc
---
description: Live Audit Workbench — sync run-state.json while running /audit
alwaysApply: false
---

# Live Audit Workbench (auto with hooks)

When the user runs **`/audit`**, a website audit, or **交付验收**:

1. **Initialize** (if not done): `./scripts/audit-run-init.sh "<target-url>"` — hooks open `workbench/live/` in the browser.
2. **Update every stage**: write `validation/artifacts/<runId>/run-state.json` per `live-run-protocol.md` (`activeAnnotation`, step `in_progress` / `completed`).
3. **Append events**: one JSON line per action to `run-events.ndjson`.
4. **Chat sync**: emit `Progress Update [n/m]` matching the same stage/step (see `progressive-reporting.md`).
5. **Finish**: write `audit-report.json` in the run folder; set `run-state.status` to `completed`.

The user may be watching **http://127.0.0.1:8765/workbench/live/** — do not leave the UI frozen while only updating chat.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free