check

Name: check
Availability: InStock
Author: Tw93

Analyze repository diffs to surface release-safe decisions and verification commands.

6.8k|402|Updated Mar 12, 2026

Search Tags:#automation #verification #diff #code-review #project-context #release-gating

Ready to run

npx skills add https://github.com/tw93/Waza --skill check-tw93

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check
Source: https://github.com/tw93/Waza/tree/main/plugins/waza/skills/check
Command: npx skills add https://github.com/tw93/Waza --skill check-tw93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyzes repository changes to surface release-safe decisions, maintain governance, and coordinate follow-through across teams.

Core Features & Use Cases

Monitors diffs, triages changes, and surfaces evidence for decision-making during PR reviews, merges, and releases.
Integrates with project context extraction and safety gates to support audit-like checks and compliance.
Provides a structured workflow surface and templates for next steps, including suggested commands and status signals.

Quick Start

Run the /check workflow against your repository and share the diff you want analyzed.

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 release gating for my repository diffs?▼

Automate code review by analyzing repository diffs to surface release-safe decisions and actionable follow-through items. The workflow monitors changes, infers constraints from manifests and CI workflows, and outputs a ship-ready surface with verification commands and evidence.

What is the best way to triage PR changes for release safety and compliance?▼

Triage PR changes by applying project context extraction and safety gates to audit repository diffs. This process surfaces evidence for decision-making during merges, ensuring compliance and maintaining governance across teams.

Does this code review workflow work across different programming languages and CI environments?▼

Yes, the code review workflow applies to PR reviews, release gating, and project audits across languages and workflows. It infers constraints directly from your public docs, manifests, and CI workflows to produce structured verification.

How do I generate public reply templates and verification artifacts for a project audit?▼

Generate public reply templates and verification artifacts by running the check workflow against your repository diff. It produces a structured surface with status signals, suggested commands, and evidence for decisions.

Can I use this release gating process without configuring external dependencies?▼

Yes, you can use this release gating process without external dependencies. It relies on internal scripts to analyze repository changes and infer project constraints directly from your existing manifests and CI workflows.

When should I not use automated diff analysis for merge decisions?▼

Avoid using automated diff analysis when your repository lacks public docs, manifests, or CI workflows for constraint inference. The process requires project context extraction to surface accurate release-safe decisions and governance evidence.