skills.rest
jeremy-newhouse
jeremy-newhouseCOMMUNITY
Explore all skills by this author →
GitHub

wa:validate-code

Validate code changes with severity-filtered findings across selected rigor modes.

Updated Mar 26, 2026
Search Tags:#code review#pull request#quality reporting#severity filtering#Git diff#language-aware analysis#rigor modes
One-click install
npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wa:validate-code
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/validate-code
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-validate-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines language-aware code review by automatically scoping changes, selecting the best available review mechanism, and reporting findings filtered by your chosen rigor level.

Core Features & Use Cases

  • Mode-aware severity filtering: Shows only CRITICAL findings in lite mode, adds WARNING in standard mode, and includes INFO in strict mode.
  • Smart review mechanism selection: Uses Greptile on open PRs when configured, otherwise falls back to a code-review plugin, and finally to ECK reviewer agents as a safety net.
  • Stage-based reporting with status updates: Updates a visible statusline at each stage and resets it on completion.
  • Targeted review scope: Reviews either a specified file/path or the set of changed files derived from git diff.

Quick Start

Run wa:validate-code against your changes by giving a file path like path/to/file.ts or by running it without an argument to review the current branch’s diff.

Frequently Asked Questions about wa:validate-code

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

FAQPage Schema
How do I review code changes filtered by severity?▼

To review code changes filtered by severity, run a validation against your git diff or a specified file path. The review mechanism reports findings based on your chosen rigor mode, showing only critical, warning, or info-level results.

Can I run a targeted code review on a specific file path?▼

Yes, you can run a targeted code review on a specific file path by providing it as an argument. Without an argument, the review automatically scopes to the set of changed files derived from your current branch's git diff.

How does pull request review work when Greptile is configured?▼

Pull request review uses Greptile automatically when configured for open PRs. If Greptile is unavailable, the review falls back to a configured code-review plugin, and finally to ECK reviewer agents as a safety net.

What is the difference between lite, standard, and strict rigor modes?▼

Lite mode shows only critical findings, standard mode adds warning findings, and strict mode includes info-level guidance. These rigor modes filter the code review output so you see only the severity of issues relevant to your workflow.

Do I need a code-review plugin to validate git diff changes?▼

No, you do not need a specific code-review plugin to validate git diff changes. The validation process uses Greptile if configured, otherwise it falls back to a code-review plugin, and finally to ECK reviewer agents as a safety net.

Related Skills

Explore More Software Engineering Skills→
reedomreedom

collect-commits-and-files

Collect and categorize changed files from Git for review workflows.

Community
Advanced
jhlee0409jhlee0409
7

afc:pr-comment

Post severity-categorized review comments to GitHub Pull Requests.

Community
Advanced
t-miura-024t-miura-024

mt-check-branch-diff

Identify Git branch differences via merge-base and collect changed files.

Community
Intermediate
JonghakseoJonghakseo
13

stress-interview

Coordinate parallel verification, code review, and adversarial analysis of software changes.

Community
Advanced