flext-refactoring-workflow

Guide bottom-up refactoring of the FLEXT monorepo with Make target validation.

Updated May 20, 2025
One-click install
npx skills add https://github.com/flext-sh/flext --skill flext-refactoring-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flext-refactoring-workflow
Source: https://github.com/flext-sh/flext/tree/main/.claude/skills/flext-refactoring-workflow
Command: npx skills add https://github.com/flext-sh/flext --skill flext-refactoring-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, step-by-step process for refactoring code within the FLEXT ecosystem, ensuring code quality, maintainability, and adherence to architectural standards through automated checks and defined workflows.

Core Features & Use Cases

  • Guided Refactoring: Offers a clear, tiered approach to making code changes, minimizing the risk of introducing regressions.
  • Automated Quality Gates: Integrates with make targets for linting, type checking, testing, and security analysis.
  • Use Case: When updating a core library in flext-core, use this Skill's workflow to systematically refactor the code, validate changes against defined quality thresholds, and ensure all dependent services are updated correctly before committing.

Quick Start

Follow the refactoring steps outlined in the skill to update the flext-core module.

Frequently Asked Questions about flext-refactoring-workflow

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

FAQPage Schema
How do I refactor Python code in a monorepo without breaking dependencies?

A guided refactoring workflow enforces architectural tier rules and runs standardized Make targets, ensuring code changes in monorepos do not break cross-project dependencies.

What is the best way to enforce code quality gates during refactoring?

Integrating automated Make targets for linting, type checking, testing, and security scans into a systematic refactoring workflow enforces code quality gates before committing changes.

How does a bottom-up refactoring process handle architectural tier rules?

A bottom-up refactoring process guides changes from foundational layers upward, validating lower-level libraries first to ensure compliance with architectural tier rules before updating dependent services.

Can I use Make targets for CI/CD validation in a Python refactoring workflow?

Yes, you can use Make targets for CI/CD validation in a Python refactoring workflow to systematically trigger linting, type checking, testing, and security scans against defined quality thresholds.

When do I need a systematic refactoring workflow for cross-project dependencies?

You need a systematic refactoring workflow for cross-project dependencies when updating shared core libraries, ensuring all dependent services are validated against quality thresholds before committing.