Busirocket Refactor Workflow

What it does

This skill, Busirocket Refactor Workflow, automates backend workflow refactoring using Busirocket's AI to optimize code structure and performance. It provides strict, step-by-step guidance focused on maintaining high code quality during the refactoring process. The skill is designed to enforce specific rules and checks, ultimately aiming for smaller files with a single export per file.

When to use it

This skill is helpful when:

• Refactoring files containing multiple exports.
• Splitting components, hooks, or utility functions into smaller, more manageable files.
• Moving inline type definitions to dedicated types/ files.
• Ensuring quality checks are performed after each refactor.
• Addressing files with multiple responsibilities by splitting them.

Key capabilities

• @file Refactor Workflow: Provides a one-shot refactoring process with strict constraints (one export per file, no inline type declarations in non-type files, and no helper functions within components/hooks).
• Mandatory Post-Refactor Checks: Enforces running standard project checks (e.g., yarn check:all) after each refactor as a quality gate.
• Decision Rules for Splitting Files: Offers heuristics to determine when files should be split based on responsibilities and content.
• File Size Guidelines: Provides targets and maximum line limits for individual files.
• Rule-Based Guidance: Includes detailed rule files explaining best practices, code examples (both correct and incorrect), and context for refactoring decisions.

Example prompts

Here are some example prompts you could use with an AI agent equipped with this skill:

• "Refactor this file using the @file Refactor Workflow."
• "Split this component into smaller files according to the decision rules."
• "Move these inline types to a types/ directory and refactor accordingly."

Tips & gotchas

• Mandatory Checks: Always run your project's standard checks after using this skill. Failure to do so will prevent successful refactoring.
• Strict Constraints: The @file workflow enforces strict rules; ensure your code adheres to them before initiating the refactor.
• Rule Documentation: Refer to the individual rule files (e.g., rules/refactor-file-workflow.md) for detailed explanations and examples.