modernize-python-repo

Migrate Python repositories to pyproject.toml and adopt Ruff.

1|Updated Feb 18, 2026

Search Tags:#python #modernization #ruff #ci-cd #pyproject #danger

Ready to run

npx skills add https://github.com/fhrbata/idf-tools-cursor-skills --skill modernize-python-repo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: modernize-python-repo
Source: https://github.com/fhrbata/idf-tools-cursor-skills/tree/main/skills/modernize-python-repo
Command: npx skills add https://github.com/fhrbata/idf-tools-cursor-skills --skill modernize-python-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides modernization of Python repositories: pyproject.toml migration, Ruff adoption, config consolidation, CI/CD and Danger workflow updates (GitHub and GitLab). Use when modernizing a Python repo, migrating from setup.py, adopting Ruff, updating Espressif GitHub/GitLab workflows, or migrating from espressif/github-actions/danger_pr_review to shared-github-dangerjs.

Core Features & Use Cases

Pyproject.toml migration across projects to consolidate build tooling.
Ruff adoption and code-quality tooling integration with minimal config churn.
CI/CD and GitHub/GitLab workflow updates, including Danger workflow migration to shared-github-dangerjs.
Use Case: Teams modernizing legacy Python repos and standardizing tooling.

Quick Start

Run the modernization workflow on your Python project to migrate to pyproject.toml, adopt Ruff, and consolidate configurations.

Frequently Asked Questions about modernize-python-repo

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

FAQPage Schema

How do I migrate a Python project from setup.py to pyproject.toml?▼

Migrating from setup.py to pyproject.toml is achieved by consolidating build tooling and configurations into a modern standard file. This workflow automates that migration to standardize Python repository setups with minimal churn.

What is the best way to adopt Ruff for Python code quality?▼

Adopting Ruff is handled by integrating the linter and consolidating code-quality tooling configurations. This process applies Ruff to your project while minimizing config churn across existing files.

Can I update GitHub and GitLab CI workflows for Danger at the same time?▼

Yes, you can update GitHub and GitLab CI workflows simultaneously. The modernization process handles Danger workflow migrations, including moving from espressif/github-actions/danger_pr_review to shared-github-dangerjs with cross-platform considerations.

Does this modernization workflow support migrating Danger workflows on both GitHub and GitLab?▼

Yes, the workflow supports Danger workflow migration on both GitHub and GitLab. It specifically migrates projects from espressif/github-actions/danger_pr_review to shared-github-dangerjs while addressing cross-platform CI considerations.

Why consolidate configurations when modernizing a Python repository?▼

Consolidating configurations when modernizing a Python repository reduces tooling fragmentation. By moving to pyproject.toml and adopting Ruff, teams standardize workflows and minimize config churn across legacy setups.