back
loading skill details...
Run a Meticulous test run after implementing a frontend change, then hand off to the `meticulous-review` skill to classify each visual change as intended or…
To test a frontend change using Meticulous, follow the workflow below step by step, using the CLI or MCP commands as described. Before starting, run the meticulous-cli-update skill to ensure the Meticulous CLI and skills are up to date — unless it has already run earlier in this conversation, in which case skip it. If you are already given a test run id, skip to Step 4. Step 1 -- Build the frontend Find out what build artefact Meticulous expects by checking .github/workflows/ for one of the following steps: uses: alwaysmeticulous/report-diffs-action/upload-assets@v1 — build assets uses: alwaysmeticulous/report-diffs-action/upload-container@v1 — docker image Build the frontend following the same instructions as used in the GitHub workflow. Step 2 -- Upload the build Register the build as a reusable deployment with agent upload-build. This uploads the artefact and prints a deploymentId to stdout — it does not trigger a run yet.
don't have the plugin yet? install it then click "run inline in claude" again.