DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to block bad commits with lint and version drift checks with Agentic Playwright

Run the bundled lint, skill drift, and version checks so broken rules or mismatched versions never get committed.

Who it is forA team lead or maintainer who keeps a shared test scaffold and wants consistent rules across contributors.

The problemRule files, skill references, and version numbers drift apart over time, and contributors may not notice until CI fails.

The outcomeClear pass or fail results from the drift and version checks, run locally before a commit or in CI.

What you need first

  • Node.js v22.x or later
  • npm v10.x or later
  • An empty directory or empty git repo for the test project
  • A web application URL to test, or the --demo option to try the bundled demo app

Steps

  1. Run npm run check:skills-drift to confirm Constitution rules stay anchored in their owning skill.
  2. Run npm run check:skills-references to catch broken pointers and anchors across the rule trees.
  3. Run npm run check:version to confirm VERSION, package.json, and the latest CHANGELOG heading match.
  4. Run npm run skills:verify to re-hash the vendored skills and detect drift from the lock file.

Prompt for your agent

In the agentic-playwright repo, run `npm run check:skills-drift`, `npm run check:skills-references`, `npm run check:version`, and `npm run skills:verify`. Expected output: each command exits with a clear pass or a non-zero drift error. Verify all four exit with status zero before reporting success.

Caveat. The README says these checks run from the Husky pre-commit hook and CI, so they only guard commits in a repo where those hooks are installed.

Share: X LinkedIn Hacker News Email Copy link

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 [email protected] and we will look at it promptly. Full disclaimer page