flext-development-workflow

Set up a monorepo development workflow with Poetry, Makefiles, and pre-commit hooks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a verified, end-to-end development workflow for the FLEXT monorepo, ensuring consistency and efficiency in coding, testing, and validation.

Core Features & Use Cases

  • Standardized Toolchain: Integrates Ruff, Pyrefly, and Pytest for linting, type checking, and testing.
  • Efficient Development Loop: Guides developers through editing, quick feedback, and pre-commit validation.
  • Use Case: A new developer joins the FLEXT team and needs to quickly set up their environment and start contributing to the flext-core project, understanding the expected development practices and tools.

Quick Start

Follow the workspace setup instructions to initialize your development environment.

Frequently Asked Questions about flext-development-workflow

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

FAQPage Schema
How do I set up a Python monorepo development workflow with Poetry and pre-commit hooks?

A Python monorepo development workflow using Poetry manages dependencies and coordinates cross-project validation through Makefiles, while pre-commit hooks enforce code quality conventions across all subprojects.

What's the best way to configure Ruff and Pyrefly for linting and type checking in a monorepo?

Configuring Ruff and Pyrefly in a monorepo involves establishing strict adherence to defined linting and type-checking conventions, ensuring code quality is validated efficiently during the development loop before commits.

How do I run cross-project validation tests using Pytest in a monorepo?

Cross-project validation tests using Pytest in a monorepo are coordinated through Makefiles, which orchestrate the execution of testing conventions across multiple projects to ensure integrated code quality.

Does this development workflow require any specific CI/CD pipeline configuration?

The development workflow establishes CI/CD conventions through pre-commit hooks and standardized toolchain setup, ensuring code quality via Ruff, Pyrefly, and Pytest without requiring external pipeline dependencies.

Can I use this monorepo workflow without Makefiles for coordinating tasks?

Makefiles are integral to this monorepo workflow as they coordinate cross-project validation and manage the development loop. Removing them would require an alternative task runner to maintain the same validation efficiency.

Why does my pre-commit hook fail when running Ruff linting in the monorepo?

Pre-commit hook failures during Ruff linting typically occur when code does not adhere to the strict conventions defined in the workflow, requiring edits to meet linting standards before completing the commit.