review-skill-changes

Review uncommitted reatom-skill changes and validate Reatom claims.

4|Updated May 12, 2026
One-click install
npx skills add https://github.com/Guria/reatom-skill --skill review-skill-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-skill-changes
Source: https://github.com/Guria/reatom-skill/tree/main/.agents/skills/review-skill-changes
Command: npx skills add https://github.com/Guria/reatom-skill --skill review-skill-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you safely and effectively review uncommitted changes in the reatom-skill repository so the skill docs and guidance stay high-quality, consistent, and Reatom-accurate.

Core Features & Use Cases

  • Local doc and reference review: Inspect diffs and adjust wording for clarity, correctness, and alignment with skill best practices.
  • Reatom-claim validation: Cross-check Reatom-specific guidance against the upstream Reatom codebase to avoid unsupported or speculative statements.
  • Native, non-leaky rewriting: Rewrite edits so they read naturally in the target document without session-specific leakage, random local artifacts, or unrelated project details.

Quick Start

Use this skill when you need to review and improve local uncommitted doc or reference edits in the reatom-skill repo, and ask it to rewrite the changed sections so they match the repository’s tone and correctly validate technical claims against Reatom.

Frequently Asked Questions about review-skill-changes

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

FAQPage Schema
How do I review uncommitted git diff changes to markdown documentation?▼

To review uncommitted git diff changes to markdown documentation, inspect the modified SKILL.md frontmatter and README text, then rewrite the sections to improve technical correctness and remove session-specific leakage.

What is the best way to validate Reatom-specific guidance in skill docs?▼

Validating Reatom-specific guidance requires cross-checking technical claims against the upstream Reatom codebase to avoid unsupported statements and ensure documentation accuracy during maintenance tasks.

How do I remove session leakage from local repository edits?▼

To remove session leakage from local repository edits, rewrite the modified content so it reads naturally in the target document without random local artifacts or unrelated project details.

Can I use a read-only git inspection to review skill maintenance changes?▼

Yes, you can use read-only git inspection to safely review uncommitted repository changes in reatom-skill, ensuring docs stay high-quality and consistent without altering the working tree state.

Does reviewing skill documentation require validating references against upstream source?▼

Yes, reviewing skill documentation requires validating modified references and technical claims against the upstream source when possible to ensure internal consistency and Reatom accuracy.

When do I need to rewrite modified markdown content during a documentation review?▼

You need to rewrite modified markdown content during a documentation review when uncommitted edits contain speculative statements, inconsistent tone, or session-specific artifacts that deviate from skill best practices.