smithery/igorwarzocha

repo-maintenance

|- Maintain repository integrity and documentation. Use for auditing structure, checking config validity, and reviewing inventory. Use proactively to validate the repository or sync documentation. - user: "Validate the repo" → run audit_repo.py - user: "Check agents" → run audit_repo.py, review errors - user: "Update documentation" → run sync_docs.py - user: "Check for issues" → run full audit

Installation

$ npx skills add smithery/igorwarzocha --skill repo-maintenance

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/igorwarzocha · top by installs.

npx skills add smithery/igorwarzocha

Browse all from smithery/igorwarzocha

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents opencode

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,608 B
  • docs SUMMARY.md 440 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Repository Maintenance Skill

This skill provides the tools to act as a Repo Custodian.

<instructions>

Validate Repository

Ensure configuration files (agents, commands, skills) are valid.

  • Command: python3 .opencode/skill/repo-maintenance/scripts/audit_repo.py

Sync Documentation

Report on repository inventory and suggest whether docs need updating.

  • Command: python3 .opencode/skill/repo-maintenance/scripts/sync_docs.py

</instructions>

<workflow>

After a Failed Audit

When the audit reports errors or warnings:

  1. Read affected files - MUST read each file listed in the output
  2. Analyze issues - Understand what changes would fix each issue
  3. Ask the user - MUST use question tool to confirm which fixes to apply
  4. Apply selectively - Only fix what the user approves

MUST NOT auto-fix all issues. Mass changes can break working configurations.

</workflow>

<reference>

Standards

Refer to references/validation-rules.md for:

  • YAML Frontmatter Schema
  • Description patterns (agents, commands, skills)
  • RFC+XML compliance requirements
  • Post-audit workflow details

</reference>