OpenSourceManagement
Triages open issues, pull requests and GitHub Discussions across the principal's own...
Install
npx skills add danielmiessler/LifeOS --skill OpenSourceManagement -g -a claude-code -y- Repository
- danielmiessler/LifeOS19.7k
- Category
- Git and review
- Updated
- 8d ago
- License
- MIT
- Context cost
- Mediumabout 2,234 tokens
- Runs scripts
- Yes, review before use
What it does
Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo public (readiness audit, fresh-history export, README and social image), stopping at the principal's go-ahead. USE WHEN open source issues, pull requests, check PRs, review PRs, check issues, community discussions, community activity, what needs attention, open source state, marker comment, triage comment, new open source models, latest open-weight models, what should I pull into Ollama, do we have this model, new Ollama models, local models, is this repo public-ready, take this repo public, open source this, public release on GitHub. NOT FOR triaging repos outside the configured list, LifeOS releases, internal work trackers, or running/prompting local models.
OpenSourceManagement
Contents: Ideal State · Intent Routing · Repos · Quick Reference · Data & Config · Gotchas · Examples
Triages and manages GitHub activity across the principal's open source repos, the OSS_REPOS list in Config.md. Repos outside that list are out of scope; when Config.md routes one elsewhere (for example a repo another skill triages), point there. Through the gh CLI it checks and prioritizes issues, recommends which PRs to merge or review, reads discussions, gives a cross-repo state snapshot, and posts a single bot comment that edits in place via hidden HTML markers instead of stacking new comments each time.
Ideal State
- Every report comes from this session's live
ghfetch, structured per repo, with items ranked by urgency and impact, each repo's community mood rated (positive, neutral, negative), and specific next actions with suggested responses, written direct and actionable. - A fetch that failed or hit its limit is named as a hole or a truncation, never rendered as a quiet repo.
- No public "fixed", "merged" or "done" claim goes out before the change lands in the source of truth (Gotchas: FIX-IN-SOURCE-FIRST), and a recurring bot note is one marker comment edited in place, never a stack.
- A private repo goes public only as an audited, fresh-history export that reads READY, with a problem-first README, a license and a social preview image, and only on the principal's word naming that repo.
- Local-model checks name what is new in the Ollama library, whether each fits and is already on the local model box, and leave every pull to the principal.
