repo-reviewer

Name: repo-reviewer
Availability: InStock
Author: Rich

Audit code repositories for duplication, stale files, and structural inefficiencies.

Updated Nov 5, 2025

Search Tags:#code quality #code review #refactoring #code hygiene #repository audit #dry principles

Ready to run

npx skills add https://github.com/RichJacobs69/job-analytics --skill repo-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-reviewer
Source: https://github.com/RichJacobs69/job-analytics/tree/main/.claude/skills/repo-reviewer
Command: npx skills add https://github.com/RichJacobs69/job-analytics --skill repo-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining a clean, organized, and efficient codebase by proactively identifying and rectifying issues such as code duplication, stale files, and poor repository structure.

Core Features & Use Cases

Code Auditing: Identifies duplicate code, suggesting consolidation opportunities.
Stale Content Detection: Flags outdated documentation and unused files.
Structural Review: Assesses directory organization and naming consistency.
Use Case: A development team can use this Skill to perform a quarterly repository health check, ensuring the codebase remains maintainable and adheres to best practices.

Quick Start

Use the repo-reviewer skill to audit the current repository for any issues.

Frequently Asked Questions about repo-reviewer

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

FAQPage Schema

How do I audit my code repository for duplication and stale files?▼

Auditing a code repository for duplication and stale files involves analyzing shell commands and file structures to identify duplicate code, outdated documentation, and unused files. This Skill enforces DRY principles to improve overall maintainability.

What is the best way to enforce DRY principles in a large codebase?▼

The best way to enforce DRY principles involves auditing directories and configurations to identify structural inefficiencies and consolidation opportunities. This Skill assesses directory organization and naming consistency to maintain code hygiene.

Can I identify dead code and unused files using a repository audit?▼

Identifying dead code and unused files through a repository audit is supported by this Skill. It flags outdated documentation and unused files by analyzing directory organization, configuration, and code scopes to rectify poor repository structure.

Does this code review tool require any external dependencies to run?▼

This code review tool requires no external dependencies to run. It operates independently using shell commands and file analysis to perform repository health checks and structural reviews.

What are the limitations of using shell commands for code hygiene reviews?▼

Using shell commands for code hygiene reviews limits analysis to file and directory structures rather than runtime behavior. This approach scopes documentation, code, and configuration to enforce DRY principles but does not execute tests.