skills.rest
Deadpool042
Deadpool042COMMUNITY
Explore all skills by this author →
GitHub

repo-refactor

Audit and refactor repository modules while preserving project contracts.

Updated Aug 27, 2026
Search Tags:#codebase#audit#refactor#contracts#repo#safeguards
One-click install
npx skills add https://github.com/Deadpool042/Creatyss --skill repo-refactor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-refactor
Source: https://github.com/Deadpool042/Creatyss/tree/main/.agents/skills/repo-refactor
Command: npx skills add https://github.com/Deadpool042/Creatyss --skill repo-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill executes a bounded set of repository changes and refactors while preserving the project's contracts and aligning with the canonical doctrine and current repo structure.

Core Features & Use Cases

  • Audit and perform scoped refactors within the defined boundaries, ensuring no contract violations.
  • Respect repository architecture and interfaces, applying changes only where necessary.
  • Use-case: Safely refactor a module to improve readability or performance without altering public behavior.

Quick Start

Execute a targeted refactor pass on the designated module and review the diffs before committing.

Frequently Asked Questions about repo-refactor

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

FAQPage Schema
How do I safely refactor a module without breaking public contracts?▼

Bounded refactoring preserves contracts by auditing the codebase before edits and limiting changes to necessary files. It validates modifications using type checks, linting, and targeted tests to ensure no contract violations occur.

What is a bounded repository refactor?▼

A bounded repository refactor automates a scoped set of codebase changes while preserving the project's contracts. It aligns modifications with the canonical doctrine and respects existing repository architecture.

Can I use automated refactoring on a local codebase with strict canonical doctrine?▼

Yes, automated refactoring works on local codebases with a canonical doctrine. The process enforces auditing before edits and restricts changes to necessary files to maintain strict architectural compliance.

What is the best way to audit a codebase before applying interface-preserving changes?▼

The best way to audit a codebase for interface-preserving changes is to analyze the canonical doctrine and repository structure first. This ensures changes apply only where necessary and prevents public behavior alterations.

How do I validate codebase changes after a scoped module refactor?▼

To validate codebase changes after a scoped module refactor, run type checks, linting, and targeted tests. This validation ensures the refactor maintains contract compliance and does not alter public behavior.

Why does my repository refactor alter public module behavior?▼

Your repository refactor alters public behavior if it does not respect the canonical doctrine or repository interfaces. Applying changes beyond necessary files without auditing boundaries causes contract violations.

Related Skills

Explore More Software Engineering Skills→
gileckgileck

full-project-audit

Audit repository deviations from guidelines and architecture rules without code changes.

Community
Advanced
ather-techieather-techie
6

commit-message

Generate standardized git commit messages from staged changes and repository history.

Community
Intermediate
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
ShaggyDShaggyD
2

sdlc-6-code-simplification

Simplify source code by reducing structural complexity while preserving functional behavior.

Community
Intermediate