requirements-profile-selection

Classify Python dependency changes into virtual environment profiles for chatbot and image services.

7|2|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/SkastVnT/AI-Assistant --skill requirements-profile-selection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-profile-selection
Source: https://github.com/SkastVnT/AI-Assistant/tree/main/.github/skills/requirements-profile-selection
Command: npx skills add https://github.com/SkastVnT/AI-Assistant --skill requirements-profile-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teach Copilot how to choose the correct dependency profile when working on the core chatbot and tools, and avoid dragging image-service dependencies into chatbot-only tasks. Use when: adding, removing, or upgrading a Python package; reviewing a dependency change; debugging import errors or version conflicts; checking whether a package belongs in venv-core or venv-image; auditing CI workflow install steps; or verifying that a chatbot-only change does not pull in image-stack packages.

Core Features & Use Cases

  • Determine whether a change in requirements.txt or profile_*.txt belongs in venv-core or venv-image based on its impact on chatbot vs image services.
  • Validate CI workflow steps to prevent leakage of image-packages into chatbot-only tasks.
  • Provide guidance on transitive dependencies and how to justify profiling decisions.

Quick Start

To classify a dependency change, determine the target service (chatbot-core vs image), consult the authoritative profile files, and produce a clear classification with justification and version constraints.

Frequently Asked Questions about requirements-profile-selection

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

FAQPage Schema
How do I classify Python dependencies for different virtual environments?

To classify Python dependencies, analyze package changes against authoritative profile files to determine their impact on chatbot versus image services, then assign them to venv-core or venv-image with version constraints and justification.

How do I prevent image-service dependencies from leaking into chatbot-only tasks?

Prevent dependency cross-contamination by validating CI workflow install steps and requirements.txt changes against authoritative profile files, ensuring image-stack packages are not pulled into chatbot-only virtual environments.

What is the best way to assign requirements.txt changes to the correct venv profile?

The best way to assign requirements.txt changes is to consult the authoritative profile files, identify the target service impact, and map the dependency to venv-core or venv-image using chunk mappings with version constraint justifications.

Why does my CI workflow install wrong Python packages for chatbot-core tasks?

Your CI workflow likely installs wrong packages because dependency changes were not classified against profile files, causing image-service dependencies to leak into the chatbot-core virtual environment during install steps.

Can I use profile files to validate transitive dependency changes in Python PRs?

Yes, you can use authoritative profile files to validate transitive dependency changes in Python PRs by analyzing the package impact on chatbot versus image services and justifying the venv-core or venv-image classification with version constraints.