update-reqs

Bump packages in *.in files to latest PyPI versions while preserving version-specifier patterns.

10|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/reidemeister94/development-skills --skill update-reqs-reidemeister94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-reqs
Source: https://github.com/reidemeister94/development-skills/tree/main/skills/update-reqs
Command: npx skills add https://github.com/reidemeister94/development-skills --skill update-reqs-reidemeister94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bump packages in a *.in file to their latest PyPI versions while preserving each line's version-specifier pattern.

Core Features & Use Cases

  • Preserve wildcard depth: for example fastapi==0.128.* updates to the latest 0.130.* while keeping the star pattern.
  • Skip comments, blank lines, git dependencies, and lines without versions or with extras only.
  • Show the diff, apply on confirmation, then recompile the lockfile: uv pip compile <file>.in -o <file>.txt --upgrade.

Quick Start

Use update-reqs to update the target .in file in your project.

Frequently Asked Questions about update-reqs

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

FAQPage Schema
How do I update Python requirements to latest PyPI versions while keeping version specifier patterns?

To update Python requirements, this Skill bumps packages in a *.in file to their latest PyPI versions while preserving each line's existing version-specifier pattern, such as wildcards or exact pins.

How do I bump wildcard version pins in a requirements.in file without breaking the format?

Bumping wildcard version pins preserves the wildcard depth; for example, fastapi==0.128.* updates to the latest 0.130.* while keeping the star pattern intact in the *.in file.

Does updating requirements skip comments and git dependencies in *.in files?

Updating requirements skips comments, blank lines, git dependencies, and lines without versions or with extras only, ensuring only standard PyPI package pins are modified.

What is the best way to recompile a Python lockfile after bumping dependencies?

The best way to recompile a Python lockfile after bumping dependencies is running uv pip compile <file>.in -o <file>.txt --upgrade, which this Skill executes automatically after applying updates.

Can I review dependency changes before applying updates to my requirements file?

You can review dependency changes before applying updates; the Skill shows a diff of the proposed version bumps and only applies them to the *.in file after receiving your confirmation.

Does this requirements update tool work with requirements-dev.in or any custom *.in file?

The requirements update tool works with requirements.in, requirements-dev.in, or any other *.in file containing version pins and comments, applying updates uniformly across all valid files.