Skip to main content
Run any Skill in Manus
with one click
GitHub repository

LifeOS

LifeOS contains 22 collected skills from nbramia, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
22
Stars
18
updated
2026-07-10
Forks
4
Occupation coverage
4 occupation categories · 100% classified
repository explorer

Skills in this repository

implement
software-developers

Full implementation lifecycle with adversarial review using subagents

2026-07-10
address-review
software-quality-assurance-analysts-and-testers

Address PR review feedback and verify independently

2026-07-07
draft-issue
software-developers

Draft and create a GitHub issue from a description, investigation, or conversation context. Use when a problem is too large for a quick fix, when you want to propose a change for later, or when the user asks to "file an issue", "create an issue", "draft an issue", "open a ticket", or "log this for later". Also useful when another skill (like tune) determines a change is too large and needs to be tracked as an issue instead.

2026-07-07
merge-pr
software-developers

Merge a PR and update upstream GitHub issues with progress

2026-06-25
pr-check
software-quality-assurance-analysts-and-testers

Validate a PR against PR standards before requesting review

2026-06-25
persona-check
software-developers

Health-check the LifeOS persona layer (files load, /chat matches the Telegram bots per persona, no personal values leak into committed persona files, frontmatter valid) and open every persona doc in Sublime for editing.

2026-06-22
routing-health
software-developers

On-demand routing health check for /chat. Verifies every model (auto / Sonnet / Opus / Gemma-local / Claude Code) on BOTH text and voice, across every persona, and that messaging a persona in /chat is identical to messaging its Telegram bot.

2026-06-22
address-review
software-quality-assurance-analysts-and-testers

Address PR review feedback and verify independently

2026-06-14
catchup
software-developers

Synthesize recent PR activity into a cross-PR net-effects briefing

2026-06-14
draft-issue
software-developers

Draft and create a GitHub issue from a description, investigation, or conversation context. Use when a problem is too large for a quick fix, when you want to propose a change for later, or when the user asks to "file an issue", "create an issue", "draft an issue", "open a ticket", or "log this for later". Also useful when another skill (like tune) determines a change is too large and needs to be tracked as an issue instead.

2026-06-14
implement
software-developers

Full Codex implementation lifecycle for GitHub issues, pull requests, or freeform coding tasks: understand scope, plan, create a branch, write tests, implement changes, run verification, create a PR, perform adversarial review/address rounds, merge, and update linked issues. Use when the user invokes $implement, asks to implement an issue such as '#123', says 'implement this', asks for end-to-end delivery from task to PR/merge, or wants the former Claude /implement workflow in Codex.

2026-06-14
merge-pr
software-developers

Merge a PR and update upstream GitHub issues with progress

2026-06-14
mine-for-ideas
software-developers

Analyze an open-source repo and surface ideas/patterns LifeOS could learn from

2026-06-14
pr-check
software-quality-assurance-analysts-and-testers

Validate a PR against PR standards before requesting review

2026-06-14
review-pr
software-quality-assurance-analysts-and-testers

Run adversarial PR review with specialist subagents

2026-06-14
stale
software-developers

Housekeeping report — find stale PRs, orphan branches, stale issues, and stale plans

2026-06-14
standup
software-developers

Personal daily summary — what you shipped, what's in progress, what needs attention

2026-06-14
tune
software-developers

Tune LifeOS orchestrator behavior based on feedback about a bad response. Use when the user describes a problem with how LifeOS answered a query — wrong sources, too verbose, not persistent enough, poor tool selection, bad source integration, missing detail, gave up too early, etc. Also covers Codex task execution issues (scope, persistence, notification style). Makes a surgical prompt edit, branches, commits, and pushes. Trigger on: "tune", "response-tuning", "fix the prompt", "tune the response", "it didn't search enough", "too verbose", "improve the orchestrator", "the response was bad", or any feedback about LifeOS chat/orchestrator quality.

2026-06-14
sync-health
office-clerks-general-439061

Comprehensive sync + vault + LLM + service health checkup. Surfaces what's stale, what's broken, what's about to break.

2026-05-28
tune
computer-occupations-all-other

Tune LifeOS orchestrator behavior based on feedback about a bad response. Use when the user describes a problem with how LifeOS answered a query — wrong sources, too verbose, not persistent enough, poor tool selection, bad source integration, missing detail, gave up too early, etc. Also covers Claude Code task execution issues (scope, persistence, notification style). Makes a surgical prompt edit, branches, commits, and pushes. Trigger on: "tune", "response-tuning", "fix the prompt", "tune the response", "it didn't search enough", "too verbose", "improve the orchestrator", "the response was bad", or any feedback about LifeOS chat/orchestrator quality.

2026-03-08
mine-for-ideas
software-developers

Analyze an open-source repo and surface ideas/patterns LifeOS could learn from

2026-02-27
review-pr
software-quality-assurance-analysts-and-testers

Run adversarial PR review with specialist subagents

2026-02-27
LifeOS Agent Skills on GitHub | SkillsMP