repo-maintenance

To maintain repository freshness, audit content for staleness, broken links, and placeholders, then draft a change proposal using an approved template. This coordinates updates through human approval to ensure changes remain current and aligned with governance rules.

To maintain repository freshness, audit content for staleness, broken links, and placeholders, then draft a change proposal using an approved template. This coordinates updates through human approval to ensure changes remain current and aligned with governance rules.

Yes, the skill can audit examples and templates for missing dependency updates and broken links. It coordinates these findings into a change proposal, routing the corrections through human approval to guarantee safe and reviewable repository updates.

Dependency maps enforce atomic change sets by aligning updates to guides and templates with documentation standards. This traceability ensures every proposed modification is reviewed holistically, preventing partial updates from breaking the repository structure.

Yes, the change proposal workflow requires human approval before applying updates. The skill proposes changes rather than applying them directly, ensuring all modifications to prompts, skills, and guides are reviewed for safety and template compliance.

You should avoid automated application when strict governance and template compliance are required, as this skill only proposes updates. Direct modifications bypass human approval and dependency map enforcement, risking broken atomic change sets and traceability.