timothymeadows/pr-readiness-gate
skills/pr-readiness-gate/SKILL.md
Stop before pushing or opening a pull request, summarize readiness, and ask the human to confirm they are ready for PR creation.
$ install --global
skillsauthnpx skillsauth add timothymeadows/opencaw pr-readiness-gateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 4:04 AM93.9s1 file scanned
SKILL.md
- name:
- pr-readiness-gate
- description:
- Stop before pushing or opening a pull request, summarize readiness, and ask the human to confirm they are ready for PR creation.
When to use
Use when implementation and local verification for a task are complete and the next likely action is pushing a branch or opening/updating a pull request.
Output
- readiness report path
- validation summary and current branch state
- explicit user prompt asking whether they are ready for the branch to be pushed and a PR opened
Notes
- This is a hard gate: do not run
git push, create a PR, open a draft PR, update a PR branch, or enable auto-merge until the user explicitly confirms readiness after implementation. - A general implementation request is not PR approval. Ask again at completion so the human can validate locally.
- Use this gate before any
gh,githubCLI/wrapper, GitHub MCP/connector, or publishing skill that could create or update a PR. - After the user confirms, choose GitHub PR tools in this order: local
ghfirst, an availablegithubCLI executable or repository-provided GitHub CLI wrapper second, and GitHub MCP/app connector tools only when both CLI options are unavailable or unsuitable. - After the user confirms and the PR is available, immediately continue with post-PR QA.
Command
../commands/pr-readiness-check.sh [task_or_issue_ref] [validation_summary_file]
Related Skills
timothymeadows/review-isometric-production
tools
VerifiedTrustedCommunity
Review isometric and 2.5D game art for projection, tile metrics, anchors, elevation, depth sorting, occlusion, lighting, walkability, and gameplay readability. Use for isometric sprites, tiles, props, environments, VFX, maps, atlas handoffs, or style reviews.
4SKILL.mdUpdated Jun 6, 2026
timothymeadows/prepare-game-art-handoff
testing
VerifiedTrustedCommunity
Prepare game art assets for implementation handoff with style references, source/runtime file paths, atlas metadata, pivots, anchors, animation rows, collision assumptions, sorting layers, licensing, and validation checks. Use when art roles deliver assets to engineering, QA, game design, or documentation.
4SKILL.mdUpdated Jun 6, 2026
timothymeadows/maintain-art-style-contract
testing
VerifiedTrustedCommunity
Maintain, generate, or validate the host repository STYLE.md art contract from OpenCaw .styles templates. Use when visual work must preserve a project art direction, when a user asks to choose or change art styles, or when art roles need to verify that STYLE.md still references valid style templates.
4SKILL.mdUpdated Jun 6, 2026
timothymeadows/generate-style
tools
VerifiedTrustedCommunity
Generate the host repository STYLE.md by composing one or more selected templates from ./.styles/.
4SKILL.mdUpdated Jun 6, 2026