check

Automate code review, issue triage, release gating, and quality audits.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/redisread/product-stories --skill check-redisread
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/redisread/product-stories/tree/main/.agents/skills/check
Command: npx skills add https://github.com/redisread/product-stories --skill check-redisread

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of unreliable manual reviews and missed release blockers by providing a rigorous, multi-mode review system that validates code changes, triages issues, gates releases, and audits project health before anything ships to production.

Core Features & Use Cases

  • Multi-Mode Operation: Switch between default diff review, issue/PR triage, release worthiness analysis, ship/release follow-through, and project-wide audit scorecards based on user intent.
  • Safety Guardrails: Enforces worktree safety preflight, hard stops for destructive operations, and evidence-based verification before any commit, push, or publish action.
  • Specialist Reviewers: Automatically activates security and architecture specialists for high-risk diffs, and runs adversarial passes for deep reviews of auth, payments, or data mutation changes.
  • Use Case: A maintainer preparing a release can use this Skill to verify version alignment across manifests, confirm generated artifacts are regenerated, check CI status, and validate release assets before tagging and publishing.

Quick Start

Use the check skill to review the current branch diff and provide a structured report with findings, fixes, and verification steps before merging.

Frequently Asked Questions about check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review and PR triage before merging?

Automated code review and PR triage can be performed by extracting git diffs, inspecting remote state via GitHub CLI, and generating structured reports with findings, fixes, and verification steps before sign-off.

What is the best way to validate release gates and check CI status before publishing?

Validating release gates requires verifying version alignment across manifests, confirming generated artifacts are regenerated, checking CI status, and validating release assets before tagging and publishing.

Do I need git and GitHub CLI to run project-wide quality audits?

Yes, project-wide quality audits require git for diff extraction and GitHub CLI for remote state inspection, along with project-specific verification commands to validate artifacts and CI status.

How does automated code review handle high-risk diffs like auth or payment changes?

Automated code review handles high-risk diffs by activating security and architecture specialists and running adversarial passes for deep reviews of auth, payments, or data mutation changes.

What safety guardrails apply when running release readiness checks?

Release readiness checks enforce worktree safety preflight and evidence-based verification with hard stops for destructive operations before any commit, push, or publish action.