agentleFS
stunt-doublestunt-double/stuntdouble-mcp/skills/run-qa-suite/SKILL.md

run-qa-suite

Skill1 starsChanged 32 days agoMITView on GitHub

Run every Stunt Double workflow and checklist in a workspace and produce a GO, CONDITIONAL or NO-GO release-readiness report.

The file

Files
SKILL.md

Run QA suite

  1. Discover: list_workspaces(), list_workflows(workspace_id), list_checklists(workspace_id).
  2. Trigger all in parallel: run_workflow(workflow_id) and run_checklist(checklist_id) for each, collecting run IDs.
  3. Poll to completion: get_workflow_run(run_id), get_checklist_run(run_id).
  4. Report: each workflow and checklist with pass or fail; for failures the step or check, actor and what went wrong. get_workflow(workflow_id) returns recent_runs for comparison.
  5. New feedback: list_feedback(project_id, status: "new") for issues the runs surfaced, and include them.
  6. Verdict: GO (all pass, no new blockers), CONDITIONAL (minor issues only, list known issues), NO-GO (blocker failures, list what must be fixed).

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.