skills.rest
4tikhonov
4tikhonovCOMMUNITY
Explore all skills by this author →
Website𝕏@4tykhonovGitHub

code-review

Review code changes from a run and auto-fix mechanical issues.

3|1|Updated Jan 23, 2026
Search Tags:#testing#standards#auto-fix#code-quality#lint#code-review#post-run
One-click install
npx skills add https://github.com/4tikhonov/the-minority-report --skill code-review-4tikhonov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/4tikhonov/the-minority-report/tree/main/ontologies/.specsmd/fire/agents/builder/skills/code-review
Command: npx skills add https://github.com/4tikhonov/the-minority-report --skill code-review-4tikhonov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to automatically review code changes produced during a run, fix trivial issues, and surface improvements requiring confirmation, ensuring code quality after tests complete.

Core Features & Use Cases

  • Post-run code review: automatically examine files created or modified in the current run against project standards and testing results.
  • Auto-fix of mechanical issues: fix non-semantic issues while preserving behavior, guided by repository standards.
  • Suggestions requiring confirmation: propose meaningful improvements that require user approval when changes could affect behavior, security, or architecture.
  • Use Case: After a CI job finishes, receive a concise report detailing auto-fixed changes and recommended improvements for the next merge.

Quick Start

Trigger the skill after tests pass, providing input with files_created, files_modified, and run_id. The skill will review changes, apply safe auto-fixes, and present suggestions for confirmation.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automatically review code changes after a test run?▼

Post-run code review automatically examines files created or modified during a run, evaluating them against project standards and testing results to apply mechanical auto-fixes and suggest behavioral improvements.

What is the best way to auto-fix code quality issues without changing behavior?▼

Auto-fixing code quality issues involves applying only mechanical changes guided by repository standards, ensuring that fixes do not affect security, architecture, or runtime behavior.

How do I ensure code review suggestions do not break my architecture?▼

Code review suggestions are categorized by consulting repository guidelines, ensuring that any changes affecting behavior, security, or architecture always require explicit user confirmation before applying.

What files do I need to provide to trigger a post-run code review?▼

Triggering a post-run code review requires providing input containing files_created, files_modified, and run_id after your tests pass to analyze the changes against project standards.

Can I use this code review skill if my project has custom lint standards?▼

Yes, the code review skill conforms to custom repository guidelines by consulting referenced review categories and auto-fix rules to evaluate findings and apply appropriate changes.

Related Skills

Explore More Software Engineering Skills→
191854169191854169

openclaw-qa-testing

Coordinate repository-backed QA tests for OpenClaw using qa-lab and qa-channel.

Community
Advanced
archyl-comarchyl-com
1

archyl-autofix

Detect Archyl C4 model drift and generate auto-fix proposals via Change Requests.

Official
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
QunnnnQunnnn

dart-run-static-analysis

Run Dart static analysis and apply automated lint fixes.

Community
Intermediate