/SKILL.md
Lightweight engineering workflow for agent-led development. Provides plan, work, verify, ship, and analyse commands with TDD, documentation discipline, security review, code review, and quality gates.
npx skillsauth add raunakkathuria/buildwright buildwrightInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Buildwright is a lightweight engineering discipline layer: understand, test, implement, document, verify, review, ship.
Implement bug fixes, refactors, and features.
Flow: understand -> research -> plan if needed -> Red -> Green -> Refactor -> docs -> verify -> security review -> code review -> commit/ship.
For larger features, /bw-work writes docs/specs/[feature]/research.md and
docs/specs/[feature]/spec.md. For small tasks, it keeps research lightweight.
Every user-facing change must update affected docs or state why no docs apply.
Research a question or topic and produce a written deliverable. No source changes, commits, pushes, or PRs.
Run project quality gates: typecheck, lint, test, and build. Commands come from
.buildwright/steering/tech.md when present; otherwise Buildwright detects and
writes them.
Run verify, security review, Staff Engineer review, then commit, push, and open a PR. Shipping confirms documentation was updated or explicitly not applicable.
Analyse a brownfield codebase and write .buildwright/codebase/STACK.md,
ARCHITECTURE.md, CONVENTIONS.md, and CONCERNS.md. Also creates or updates
.buildwright/steering/tech.md with discovered stack and commands.
Buildwright recursively reads every .md file under .buildwright/steering/.
It installs one default steering file:
.buildwright/steering/philosophy.md — KISS, YAGNI, DRY, boring technology,
fail fast, Red -> Green -> Refactor, documentation discipline, and financial
code rules.Project-specific steering is lazy-created:
tech.md after command and stack discovery.product.md only for greenfield work or explicit product context.Buildwright uses prompt-based review personas:
Buildwright does not edit .env files, run destructive git operations, force
push, or merge PRs. It stages only files changed for the current work.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.