backend-refactor

Rewrite and clean fleet_rlm backend modules with test updates.

51|6|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Qredence/fleet-rlm --skill backend-refactor-qredence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-refactor
Source: https://github.com/Qredence/fleet-rlm/tree/main/.factory/skills/backend-refactor
Command: npx skills add https://github.com/Qredence/fleet-rlm --skill backend-refactor-qredence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplifies and stabilizes the fleet-rlm backend by rewriting unstable modules, removing deprecated code paths, and updating tests to reflect new architectures, reducing maintenance burden and improving reliability.

Core Features & Use Cases

  • Rewrites Python modules across src/fleet_rlm/runtime/, src/fleet_rlm/api/, src/fleet_rlm/integrations/daytona/, and src/fleet_rlm/integrations/database/ to align with current architecture.
  • Deletes directories or orphaned files and consolidates multiple modules into simpler, coherent units.
  • Updates or creates unit tests to validate new behavior and guard against regressions in critical backend components.
  • Removes dangling imports and ensures compatibility with Daytona 0.168.0 upgrade path.

Quick Start

Outline and execute a backend refactor plan that rewrites modules, removes deprecated files, and updates tests.

Frequently Asked Questions about backend-refactor

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

FAQPage Schema
How do I refactor Python backend modules to reduce technical debt?

To refactor Python backend modules, rewrite unstable code paths, remove deprecated files, and consolidate orphaned modules into coherent units while updating unit tests to validate new behavior and prevent regressions.

How do I clean up dangling imports and prevent side effects during a backend refactor?

Cleaning up dangling imports during a backend refactor requires enforcing strict typing, removing import-time side effects, and ensuring lint adherence across all rewritten runtime, API, and integration modules.

Does the Daytona 0.168.0 upgrade path require removing deprecated backend code?

The Daytona 0.168.0 upgrade path requires removing deprecated code paths and dangling imports to ensure integration compatibility, consolidating multiple modules into simpler, coherent units for improved reliability.

What is the best way to consolidate multiple Python modules into simpler units?

The best way to consolidate multiple Python modules is to merge orphaned files, delete obsolete directories, and rewrite the remaining code to align with current architecture while updating tests to guard against regressions.

How do I update unit tests when rewriting runtime and API modules?

Updating unit tests when rewriting runtime and API modules involves creating new test cases to validate the refactored behavior and architecture, ensuring critical backend components remain protected against future regressions.