mcpField
A
automate-project-maintenance

automate-project-maintenance

github.com/liblafDevelopment0182 installsUpdated 6w ago
Repository

About automate-project-maintenance

automate-project-maintenance is a skill for choosing and running repository maintenance steps based on inspected project files. It distinguishes Python and TypeScript workflows, invokes focused skills, and keeps remote GitHub updates preview-first.

Key features

  1. 01Detect repository type from files
  2. 02Run stack-specific maintenance steps
  3. 03Python test and documentation workflow
  4. 04TypeScript formatting checks
  5. 05Preview GitHub metadata updates

Use cases

  1. 01Choose maintenance actions for an unfamiliar repository
  2. 02Run applicable checks for a Python project
  3. 03Format and check a TypeScript project
  4. 04Preview repository metadata changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/liblaf/skills --skill automate-project-maintenance

After installing, type/automate-project-maintenancein Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Automate Project Maintenance

Use this skill after the focused maintenance skills are available. Detect the repo type from local facts, not from naming guesses.

Detection

Inspect the repo before acting.

  • Python signals:
    • pyproject.toml
  • TypeScript signals:
    • package.json

Workflow

  1. Determine whether the repo is Python, TypeScript, or other.
  2. Run only the applicable focused skills.
  3. Keep remote GitHub updates preview-first.

Python Branch

  1. Use $write-python-tests.
  2. Use $rewrite-python-docs.
  3. Use $write-root-readme.
  4. Run rumdl fmt . and treat findings as weak hints.
  5. Run mise run lint.
  6. Run mise run docs:build.
  7. Run nox.
  8. Use $sync-github-repo-metadata in preview mode.

TypeScript Branch

  1. Use $write-root-readme.
  2. Run rumdl fmt . and treat findings as weak hints.
  3. If TypeScript or JavaScript files were edited, run biome check --write.
  4. Use $sync-github-repo-metadata in preview mode.

Other Repos

  • Apply the appropriate maintenance steps based on the detected technology stack.
  • Do not assume both branches must edit files in the same run.

Comments

Markdown supported