PR

project-maintenance

Handles dependency and documentation updates to ensure the Farmadil System remains accurate during development.

Install

mkdir -p .claude/skills/project-maintenance && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15018" && unzip -o skill.zip -d .claude/skills/project-maintenance && rm skill.zip

Installs to .claude/skills/project-maintenance

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when changing the Farmadil System project, especially when adding new libraries, updating requirements.txt, or making major changes that require updating DESCRIPCION_SISTEMA.md.
181 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Check for new external dependencies
  • Add new Python libraries to `requirements.txt`
  • Install new libraries in the active virtual environment
  • Update `DESCRIPCION_SISTEMA.md` for major changes
  • Verify application startup or test pass

How it works

This skill outlines a procedure to ensure that new Python libraries are recorded in `requirements.txt` and installed, and that `DESCRIPCION_SISTEMA.md` is updated for significant project changes.

Inputs & outputs

You give it
Changes to the Farmadil System project, especially new libraries or major code/architecture changes
You get back
An updated `requirements.txt` and `DESCRIPCION_SISTEMA.md`, with verified application functionality

When to use project-maintenance

  • Updating project dependencies
  • Syncing requirements.txt
  • Updating system descriptions
  • Reflecting architectural changes
  • Verifying dependency documentation

About this skill

Project Maintenance

When to Use

  • Add or update third-party Python libraries
  • Make changes that require updating requirements.txt
  • Make important code, architecture, database, or workflow changes
  • Keep DESCRIPCION_SISTEMA.md aligned with the current system state

Procedure

  1. Check whether the change introduces any new external dependency.
  2. If a new library is used, add it to requirements.txt and install it in the active virtual environment.
  3. If the change is important enough to affect how the system is described, update DESCRIPCION_SISTEMA.md in the same change.
  4. Verify the application still starts or the affected tests still pass.
  5. Confirm that the documentation and dependency files match the implemented change.

Completion Checks

  • No new library is used without being recorded in requirements.txt
  • DESCRIPCION_SISTEMA.md reflects major functional or architectural changes
  • The venv and dependency list stay in sync with the codebase

When not to use it

  • When changes do not involve new libraries
  • When changes are minor and do not affect system description

Limitations

  • This skill is for changing the Farmadil System project
  • This skill is for adding new libraries, updating requirements.txt
  • This skill is for making major changes that require updating DESCRIPCION_SISTEMA.md

How it compares

This skill standardizes the maintenance process for the Farmadil System, ensuring dependency files and system documentation remain synchronized with code changes, unlike ad-hoc updates.

Compared to similar skills

project-maintenance side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
project-maintenance (this skill)04moNo flagsBeginner
codex-cli-bridge99moReviewIntermediate
droidrun-docs12moReviewIntermediate
mflux-release15moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry