Validate pull requests for zero new SonarCloud issues before merge.
npx skills add https://github.com/gvinokur/qatar-prode --skill code-reviewer-gvinokur
Please help me install this Agent Skill. Skill: code-reviewer Source: https://github.com/gvinokur/qatar-prode/tree/main/.claude/skills/code-reviewer Command: npx skills add https://github.com/gvinokur/qatar-prode --skill code-reviewer-gvinokur
Prevents merging pull requests that introduce new SonarCloud issues or stale documentation by performing a strict, reproducible pre-merge validation workflow and a mandatory documentation audit before marking work complete.
Run the validation flow after the user confirms "code looks good" so the skill can mark the PR ready, wait for CI and SonarCloud, enforce zero new issues, and perform the pre-merge documentation audit.
High-intent search queries and answers about installing and using this skill.
To enforce zero new SonarCloud issues before merging, you can run a pre-merge validation workflow that fetches SonarCloud analysis for the PR, requires zero new issues of any severity, and verifies coverage thresholds on new code.
A pre-merge documentation audit is a line-level accuracy check comparing CODE-STRUCTURE layer files against changed source files, blocking story completion until the documentation accurately reflects the code deviations.
Plan reconciliation compares the story plan and commit history to actual code changes, recording amendments when deviations are found so that the final pre-merge state matches the intended feature scope.
Yes, the validation workflow works with Vercel preview deployments by waiting for CI and Vercel builds, validating preview deployment accessibility, and collecting checks before running the SonarCloud quality gate enforcement.
Running SonarCloud quality gates requires the PR number, worktree path, access to SonarCloud and CI results, and the repository CODE-STRUCTURE files to perform plan reconciliation, coverage analysis, and the documentation audit.
Automated code review quality gates should not be used before the user explicitly confirms the code looks good after Vercel preview testing, as the workflow depends on this confirmation to move the PR out of draft and initiate final validation.
MFS-codeMerge a prepared pull request and deploy with canary verification.
cookeyholderSquash and merge a GitHub pull request into main after validating review feedback.
Svenja-devAutomate end-to-end and security testing for Vercel Preview Deployments with Playwright.
bailynloveAutomate pre-commit code verification with static security scanning and quality gates.
