skills.rest
archibate
archibateCOMMUNITY
Explore all skills by this author →
Website𝕏@archibateGitHub

review

Review changed files for quality issues and propose non-destructive fixes.

37|7|Updated Apr 8, 2026
Search Tags:#git#review#docs#bugs#code#ai-slop#task-create
One-click install
npx skills add https://github.com/archibate/dotfiles-claude --skill review-archibate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/archibate/dotfiles-claude/tree/main/skills/review
Command: npx skills add https://github.com/archibate/dotfiles-claude --skill review-archibate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers identify and fix bugs, AI slop patterns, and documentation gaps that appear after major changes, enabling cleaner, more reliable codebases.

Core Features & Use Cases

  • Integrated review workflow across code changes, AI prompts, and documentation
  • Automated issue creation and tracking for fixes
  • Post-change, on-demand reviews in response to user requests like "review" or "code review"

Quick Start

Ask the assistant to run a targeted review on the latest changes and propose fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code changes to find bugs and documentation gaps?▼

To review code changes for bugs and documentation gaps, you need an interactive process that identifies quality issues across modified files and proposes non-destructive fixes to preserve behavior.

How do I identify AI slop patterns in my current project changes?▼

Identifying AI slop patterns in project changes requires scanning modified files, staged changes, and repository roots to detect low-quality code and present actionable findings with readable file locations.

Can I generate an issue list for code quality issues found in staged changes?▼

Yes, you can generate a concise issue list with short codenames for code quality issues found in staged changes, which enables automated issue creation and tracking for subsequent fixes.

What's the best way to integrate code, docs, and prompt reviews after major changes?▼

The best way to integrate code, docs, and prompt reviews after major changes is using an integrated review workflow that scopes modified files and proposes fixes to ensure cleaner codebases.

Does this code review process support non-destructive fixes for modified files?▼

Yes, this code review process supports non-destructive fixes for modified files by proposing changes that preserve behavior while addressing the identified bugs, AI slop, and documentation issues.

Related Skills

Explore More Software Engineering Skills→
fredericosantosfredericosantos
1

ghp:init

Automate GitHub session triage using gh project, milestone, issue, and PR lists.

Community
Intermediate
ibalasiteibalasite

reviewdoc

Coordinates multi-agent document reviews against defined templates with iterative rounds and git tracking.

Community
Advanced
tylerjrbuelltylerjrbuell
21

update-docs

Synchronize repository documentation and agent skill files after code changes.

Community
Advanced
act70255act70255

lint-and-validate

Lint and statically analyze Node.js and Python code with ESLint, Pylint, Ruff, MyPy, and Bandit.

Community
Advanced