Refactoring Audit Workflow

Audit codebases for smells and anti-patterns, then create GitHub issues.

309|15|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/ShareX/XerahS --skill refactoring-audit-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Refactoring Audit Workflow
Source: https://github.com/ShareX/XerahS/tree/main/.ai/skills/refactoring-audit
Command: npx skills add https://github.com/ShareX/XerahS --skill refactoring-audit-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill streamlines the discovery and prioritization of code refactoring opportunities by guiding an audit workflow that uncovers smells, validates findings, and aligns them with actionable GitHub issues.

Core Features & Use Cases

  • Identify and categorize code smells (e.g., God Classes, low cohesion, OC violations) to prioritize refactoring targets.
  • Produce structured implementation plans and acceptance criteria to guide engineers and track progress.
  • Generate and file GitHub issues from vetted findings, with templates and verification steps for consistent delivery.

Quick Start

Provide a starter audit for the codebase and generate a draft GitHub issue plan.

Frequently Asked Questions about Refactoring Audit Workflow

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

FAQPage Schema
How do I audit my codebase for code smells to plan refactoring?

Auditing for code smells involves identifying anti-patterns like God Classes and low cohesion to prioritize refactoring targets. This workflow validates findings against constraints and aligns them with structured implementation plans for tracking.

Can I automatically create GitHub issues from refactoring findings?

Yes, you can automatically generate and file GitHub issues from vetted refactoring findings. The workflow uses templates and verification steps, integrating with gh CLI for automated tracking and consistent delivery.

What is the best way to prioritize code refactoring targets in a software project?

Prioritizing refactoring targets requires categorizing code smells by severity and validating constraints. A structured audit workflow uncovers anti-patterns, drafts plans, and produces acceptance criteria to guide engineering efforts.

Does this refactoring workflow require the gh CLI to track issues?

The workflow supports integration with gh CLI for automated tracking and creating GitHub issues. Using it allows you to file vetted findings directly from the generated draft plan with consistent templates and verification steps.

How do I generate implementation plans and acceptance criteria for refactoring tasks?

Implementation plans and acceptance criteria are generated by documenting actionable refactoring opportunities. The audit workflow validates constraints and drafts structured plans to guide engineers and track progress on GitHub.

What types of code smells can an audit workflow identify?

An audit workflow identifies code smells such as God Classes, low cohesion, and OC violations. Categorizing these anti-patterns helps prioritize refactoring targets and produce structured implementation plans for the project.