.claude/skills/ln-713-pip-upgrader/SKILL.md
Upgrades Python pip/poetry/pipenv dependencies with breaking change handling
npx skillsauth add cbbkrd-tech/jl-finishes ln-713-pip-upgraderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
Type: L3 Worker Category: 7XX Project Bootstrap Parent: ln-710-dependency-upgrader
Upgrades Python dependencies with automatic breaking change detection.
| Aspect | Details | |--------|---------| | Input | Project path, package manager type | | Output | Updated requirements.txt/pyproject.toml | | Supports | pip, poetry, pipenv |
See diagram.html for visual workflow.
Phases: Pre-flight → Detect Manager → Security Audit → Check Outdated → Apply Upgrades → Verify Installation → Report
| Check | Required | Action if Missing | |-------|----------|-------------------| | requirements.txt OR pyproject.toml OR Pipfile | Yes | Block upgrade | | Virtual environment active | No | Warn user (risk of system pollution) |
Workers assume coordinator (ln-710) already verified git state and created backup.
| Manager | Indicator Files | |---------|-----------------| | pip | requirements.txt | | poetry | pyproject.toml + poetry.lock | | pipenv | Pipfile + Pipfile.lock |
| Manager | Command |
|---------|---------|
| pip | pip-audit --json |
| poetry | poetry audit (via plugin) |
| pipenv | pipenv check |
| Severity | Action | |----------|--------| | Critical | Block upgrade, report | | High | Warn, continue | | Moderate/Low | Log only |
| Manager | Command |
|---------|---------|
| pip | pip list --outdated --format=json |
| poetry | poetry show --outdated |
| pipenv | pipenv update --outdated |
| Manager | Command |
|---------|---------|
| pip | pip install --upgrade <package> |
| pip (freeze) | pip freeze > requirements.txt |
| poetry | poetry update |
| pipenv | pipenv update |
| Priority | Tool | When to Use | |----------|------|-------------| | 1 | mcp__context7__query-docs | First choice for library docs | | 2 | mcp__Ref__ref_search_documentation | Official docs and PyPI | | 3 | WebSearch | Latest info, community solutions |
| Step | Tool | Parameters | |------|------|------------| | 1. Find library | mcp__context7__resolve-library-id | libraryName: "pydantic" | | 2. Query docs | mcp__context7__query-docs | query: "pydantic v1 to v2 migration breaking changes" |
| Action | Tool | Query Example | |--------|------|---------------| | Search | mcp__Ref__ref_search_documentation | "python pydantic 2 migration guide" | | Read | mcp__Ref__ref_read_url | URL from search results |
Use when Context7/Ref return no results:
"<package> python <version> breaking changes migration""<ImportError message> <package> fix"| Check | Command |
|-------|---------|
| Import test | python -c "import <package>" |
| Tests | pytest or python -m pytest |
| Field | Description | |-------|-------------| | project | Project path | | packageManager | pip, poetry, or pipenv | | duration | Total time | | upgrades[] | Applied upgrades | | verification | PASSED or FAILED |
MANDATORY READ: Load breaking_changes_patterns.md for full patterns.
| Package | Breaking Version | Key Changes | |---------|------------------|-------------| | pydantic | 1 → 2 | V1 compatibility layer needed | | sqlalchemy | 1 → 2 | Query syntax changes | | fastapi | 0.99 → 0.100+ | Pydantic v2 required |
Options:
# Upgrade scope
upgradeType: major # major | minor | patch
# Security
auditLevel: high
minimumReleaseAge: 14
# Python specific
pythonVersion: "3.12"
useVirtualenv: true
# Verification
runTests: true
| Error | Cause | Solution | |-------|-------|----------| | ImportError | Breaking API change | Search Context7/Ref for migration | | Dependency conflict | Version mismatch | Try pip-compile or poetry lock |
Version: 1.1.0 Last Updated: 2026-01-10
testing
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
development
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
development
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.
development
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.