{
 "schema_version": 1,
 "generated": "2026-10-23",
 "id": "awss1i-assay--gate-a-page-build-on-assay-exit-code",
 "repo": "awss1i/assay",
 "repo_url": "https://github.com/awss1i/assay",
 "repo_slug": "awss1i-assay",
 "title": "Stop a build when a page fails Assay checks",
 "page_title": "How to stop a build when a page fails Assay checks with Assay",
 "summary": "Use Assay's non-zero exit code to block a page from moving forward when it has a flagged problem.",
 "who": "A developer who maintains a static site and wants a script to refuse a build that contains a broken control.",
 "problem": "A broken button or a count that goes wrong can ship unnoticed when nothing checks the built page.",
 "outcome": "A script that stops with an error when Assay flags a problem and passes when the page is clean.",
 "steps": [
  "Run `pip install assay-ui` on the machine that runs the build.",
  "Run the build step that writes the built page output to a folder.",
  "Add `assay <built folder> --one-line` after the build step in your script, replacing <built folder> with the output path. (inferred, check the README)",
  "Confirm the script stops when a known broken page is used as input, then keep the step in place."
 ],
 "agent_prompt": "Add an assay check to the build script in <repo path>. After the build writes to <output folder>, run assay <output folder> --one-line and stop the script if the exit code is non-zero. Verify by running the script against a page with a known broken control and confirming it stops.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Assay only checks built output, so it will not run your build or npm install for you, and the build step must be run first.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "python",
 "requirements": [
  "Python 3.10+, or uv or pipx to install the tool",
  "A folder containing built web page output, with index.html or another page to check",
  "Internet access for the first run, when Chromium may be downloaded"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/awss1i-assay/gate-a-page-build-on-assay-exit-code/",
 "md": "https://dedupedai.com/use-cases/awss1i-assay/gate-a-page-build-on-assay-exit-code/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/awss1i-assay--gate-a-page-build-on-assay-exit-code.json",
 "api_version": "v1"
}