automate-project-maintenance
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
- Determine whether the repo is Python, TypeScript, or other.
- Run only the applicable focused skills.
- Keep remote GitHub updates preview-first.
Python Branch
- Use
$write-python-tests. - Use
$rewrite-python-docs. - Use
$write-root-readme. - Run
rumdl fmt .and treat findings as weak hints. - Run
mise run lint. - Run
mise run docs:build. - Run
nox. - Use
$sync-github-repo-metadatain preview mode.
TypeScript Branch
- Use
$write-root-readme. - Run
rumdl fmt .and treat findings as weak hints. - If TypeScript or JavaScript files were edited, run
biome check --write. - Use
$sync-github-repo-metadatain 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.
More from liblaf/skills
write-root-readme
Write or rewrite the repo-root README.md.
36write-python-tests
Write or refresh tests for Python projects. Use when Codex needs to add coverage, replace stale tests, reorganize tests under `tests/`, or lock down Python behavior from source code in repos that use `nox`, `pytest`, and `mise`.
34rewrite-python-docs
Rewrite Python docs and docstrings from source code. Use when Codex needs to refresh the docs.
34write-conventional-commit
Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.
33sync-github-repo-metadata
Inspect a repository and propose or apply GitHub About metadata updates. Use when Codex needs to infer a concise repository description and topic set from source code, package metadata, docs config, or the current README, then preview and optionally run `gh repo edit`.
33