skills.rest
thegeronimo
thegeronimoCOMMUNITY
Explore all skills by this author →
𝕏@RyskyGeronimoGitHub

static-review

Identify and prioritize defects in multi-agent tickets via read-only analysis.

44|8|Updated Jul 14, 2025
Search Tags:#security#review#code-review#reproducibility#findings#regressions
One-click install
npx skills add https://github.com/thegeronimo/hyperopen --skill static-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: static-review
Source: https://github.com/thegeronimo/hyperopen/tree/main/.agents/skills/static-review
Command: npx skills add https://github.com/thegeronimo/hyperopen --skill static-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables reviewers to perform a findings-first, read-only assessment of tickets to identify correctness gaps, regressions, security issues, race conditions, and missing tests without making style-only edits.

Core Features & Use Cases

  • Owner-like review leadership: guides the ticket review with clear findings and reproduction guidance.
  • Prioritization of critical risks: focuses on correctness, regressions, security, and data integrity.
  • Use Case: in a multi-agent ticket, generate a concise, actionable review report that documents defects and suggested fixes.

Quick Start

Provide a structured review starting from the ticket context, list concrete findings with reproduction steps, and propose concrete fixes.

Frequently Asked Questions about static-review

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

FAQPage Schema
How do I perform a findings-first code review for correctness and security defects?▼

A findings-first code review identifies and prioritizes correctness, regressions, security, race conditions, and missing tests through read-only analysis, outputting a structured report with concrete findings and reproduction steps.

What is the best way to document race conditions and regressions during ticket investigations?▼

Document race conditions and regressions by generating a concise review report that lists concrete findings, provides reproducible steps, and proposes concrete fixes without making style-only edits.

Can I use a read-only analysis approach to review multi-agent tickets without applying code edits?▼

Yes, read-only analysis assesses multi-agent tickets to identify correctness gaps and data integrity issues while explicitly avoiding style-only edits, guiding the review with clear findings and reproduction guidance.

How do I prioritize critical risks like security issues and missing tests in a code review?▼

Prioritize critical risks in a code review by focusing the assessment on correctness, regressions, security, and data integrity, ensuring the structured report highlights concrete defects and suggested fixes.

What are the limitations of a findings-first review approach for ticket investigations?▼

The findings-first review approach is limited to identifying defects and proposing fixes; it does not apply style-only edits or directly modify code, requiring concrete reproduction steps for every reported finding.

Related Skills

Explore More Software Engineering Skills→
mostafa-drzmostafa-drz
2

enrich-message

Enrich drafts with code references, ticket links, and factual data into markdown.

Community
Advanced
Chai-UnChai-Un

fix

Fix lint errors and formatting issues using yarn, prettier, and linc.

Community
Intermediate
gofhirgofhir
2

go-code-review

Analyze Go source code with golangci-lint and go vet for bugs and race conditions.

Official
Intermediate
ybbms777ybbms777
1

lint

Run standardrb, erblint, and Brakeman checks on Ruby and ERB files.

Community
Intermediate