Oss Repo Maintainer
When to Use
- User says fix README or task matches this capability
- User says prep release or task matches this capability
- User says repo maintenance or task matches this capability
- User says sync docs or task matches this capability
Workflow
- Diff README skill/file lists vs git tree.
- Flag stale counts, missing install paths, broken links.
- Propose README and CHANGELOG edits; show diff before commit.
- Run validators (tests, skill validate) if present in repo.
- Suggest conventional commit message; hitl-approver before git push.
Integrations
github-repo-scoutskill-collection-bootstrappergoal-verifier
Error Handling
| Failure | Response |
|---|---|
| Not a git repo | Limit to file review only. |
Gotchas
- Never push or publish without explicit user approval.
Safety & Ethics (Publication-Ready)
This skill is designed for public distribution. Constraints:
- Documentation accuracy focus; no unauthorized releases.
- Git push and publish require hitl-approver.
- Generic OSS workflow; no hardcoded user or org paths in instructions.
Prohibited actions
- No unauthorized access, malware, or harmful automation
- No silent exfiltration of data, credentials, or telemetry
- No destructive system changes without hitl-approver
- No publication of user PII or environment secrets in outputs
Example
Input: User request matching triggers above. Output: Structured result per workflow; local artifacts only unless user opts in.