메뉴
Use when user wants to update a pip requirements .in file (requirements.in or requirements-dev.in) with the latest PyPI versions while preserving each line's version-specifier pattern.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Compare Claude Code and Codex on the same real code-change task with isolated worktrees, identical gates, transcripts, time, and cost.
Align AGENTS.md, rules, README, plans, and chronicles with the codebase; use --clean to archive obsolete task docs into ATLAS.md.
Research current best practices and turn the evidence into a clear recommendation. Use for state-of-the-art, evidence-based, optimal-approach, comparison, or pros-and-cons questions in any field.
Clarify an ambiguous or consequential change before planning or implementation when more than one sound approach exists.
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
Create a user-requested Conventional Commit from the staged changes.
SOC 직업 분류 기준
| name | update-reqs |
| description | Use when user wants to update a pip requirements .in file (requirements.in or requirements-dev.in) with the latest PyPI versions while preserving each line's version-specifier pattern. |
| user-invocable | true |
Bump packages in a *.in file (requirements.in, requirements-dev.in, or any other) to their latest PyPI versions, preserving each line's wildcard depth. Target file from $ARGUMENTS, else requirements.in.
fastapi==0.128.* + latest 0.130.0 → fastapi==0.130.*; commitizen==4.* stays 4.*; an exact pin (pkg==1.2.3) bumps to the new exact.@ / git+), and pkg[extra] lines without a version.uv pip compile <file>.in -o <file>.txt --upgrade.The .in is hand-edited; the .txt is the generated lockfile installed by the runtime/Dockerfile (and, for requirements-dev.txt, by local dev and the CI test image).