bug-recording
Skill0 starsChanged 3 months agoUnlicenseView on GitHub
Detect whether a target web project is a React app on Node or Bun, run it, hunt for CSS / functional / render bugs with Playwright, and record an optimized video of each bug. Use when the user runs /bug-recording or asks to find and record UI bugs in an app.
In this repository16 other files it gives its agents.
- claude-agents-md/AGENTS.mdAGENTS.md
- claude-agents-md/CLAUDE.mdCLAUDE.md
- bash-skillSkill
- bundle-sizeSkill
- changelog-skillSkill
- container-skillSkill
- fact-checkerSkill
- git-gh-skillSkill
- html-researchSkill
- index-html-skillSkill
- macos-electron-appsSkill
- pr-splitterSkill
- readme-skillSkill
- rerenderSkill
- scripts-skillSkill
- stacks-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Verify these are on PATH and stop loudly if any is missing:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
bug-recording
Find bugs in a running React app and record a Playwright video of each one.
Inputs
- Target app directory. Default: current project root.
- Output directory. Default:
<target>/bug-recording-output.
Preconditions
Verify these are on PATH and stop loudly if any is missing:
node(orbun) to run the target app.ffmpegfor video encoding and the size-reduction pass.- This skill's own dependencies. If
node_modules/playwrightis absent in the skill directory, runnpm installhere, thennpx playwright install chromium.
Run
From the skill directory:
node record.mjs <target-app-dir> [output-dir]The script:
- Detects the stack from
package.jsonand lockfiles (React + Node/Bun, the package manager, the dev script). - Starts the dev server and waits until it reports a URL and is reachable.
- Discovers routes by crawling in-app links from the root page.
- Per route, captures console errors and runs three detectors:
- render: a console/page error on load or an error-boundary fallback,
- css: text clipped under
overflow:hiddenwith no ellipsis, - functional: an "increase"/"+"/"add" control that moves a numeric readout the wrong way.
- Records a narrated Playwright walkthrough per confirmed bug: starts on the
home page, moves a visible cursor to the matching nav link and clicks through
to the bug page, captions each reproduction step on screen, performs the
triggering click, and dwells on the result with the broken element
highlighted. Then converts it to H.264
.mp4, runsreduce-size.shto shrink it, and samples keyframes. - Writes
findings.jsonplusvideos/,frames/,screenshots/.
After running
- Report the bug count and where artifacts landed.
- The bugs, evidence, and per-step action logs are in
findings.json. You may read the sampledframes/*.pngto enrich each bug's reproduction steps before handing off to/bug-report.
Honest limits
The detectors target broad bug classes, not every possible bug. Report the
captured evidence, not a verdict beyond it. The agent cannot watch the .mp4 as
motion; reproduction narrative comes from the action log and sampled frames.
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
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.

