agentleFS
stunt-doublestunt-double/stuntdouble-mcp/skills/verify-change/SKILL.md

verify-change

Skill1 starsChanged 32 days agoMITView on GitHub

Verify a code change on a preview, staging or production URL by running a Stunt Double actor through the affected flows, and optionally post the results on the pull request.

23 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Verify change

  1. Context: list_workspaces(), list_projects(workspace_id). Tools that take a url (like create_checklist) find or create the project. Starting from a PR: list_pull_requests(workspace_id, owner, repo, state="open") and get_pull_request(workspace_id, owner, repo, pr_number) show which flows to exercise (needs the workspace GitHub connection). The preview URL usually comes from the user or the deploy, not the PR details.
  2. Actor: list_actors(workspace_id), reusing a QA-style actor, else create_actor(...).
  3. Checklist: create_checklist(...) with the preview URL as host, instructions for exercising the changed flows like a real user, and 4 to 8 checks covering the new behaviour, adjacent flows and error states. Phrase checks by observable behaviour, not code; one change area per checklist.
  4. Run: run_checklist(checklist_id), poll get_checklist_run(run_id) until terminal. Each check carries evidence.
  5. Report: for failures, give the evidence and likely fix; if you can edit the code, offer to fix and re-run the same checklist. With an associated PR, post a verdict line and a table of checks with comment_on_pr (owner/repo#number).
  6. Keep it: re-run on the next change to the area, or wire it up with create_workflow (see setup-guardrails).

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.