team-refactor

Plan team-based code refactoring with call-site identification and invariant validation.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/infantesromeroadrian/arca-agent --skill team-refactor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-refactor
Source: https://github.com/infantesromeroadrian/arca-agent/tree/main/template/skills/team-refactor
Command: npx skills add https://github.com/infantesromeroadrian/arca-agent --skill team-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill unit facilitates secure and comprehensive refactoring of large codebases, providing a team-based approach with explicit invariants to ensure stability and reliability.

Core Features & Use Cases

  • Team-Based Refactoring: Collaborative environment with inventory, planning, and test-guard roles.
  • Invariant-based Workflow: Focuses on maintaining defined invariants through refactoring, avoiding breakages.
  • Use Case: When you need to refactor a codebase affecting >5 files or public contracts like APIs, schemas, or exported functions.

Quick Start

Invoke /team-refactor <what-to-refactor> <invariant-description>

Frequently Asked Questions about team-refactor

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

FAQPage Schema
How do I safely refactor large codebases that affect public contracts?

Team-based refactoring manages complex code changes by assigning inventory, planning, and test-guard roles. This collaborative workflow ensures multiple developers can safely execute refactoring tasks while maintaining system stability.

When do I need an invariant-based workflow for code refactoring?

An invariant-based workflow for code refactoring is needed when changes touch public contracts like APIs, schemas, or exported functions across multiple files, ensuring defined invariants remain unbroken throughout the process.

What is the best way to coordinate team collaboration during a multi-file refactoring?

The best way to coordinate team collaboration during multi-file refactoring is to use a structured process with explicit roles for inventory, planning, and test-guard duties, ensuring reversible changes and continuous safety checks.

Can I use this refactoring approach for changes affecting fewer than five files?

This refactoring approach is designed for large scale changes affecting more than five files or public contracts. For smaller scope changes, a full team-based inventory and planning workflow may be unnecessary.

How do I start a team-based refactoring process with explicit invariants?

To start a team-based refactoring process, invoke the tool with the target refactoring description and the invariant description. This initiates the planning phase to identify call sites and validate against your specified invariants.