Menú
Keep Agentic OS worktree and work-item state clean after Jira terminal statuses or merged pull requests.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Groom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.
Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.
Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.
Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.
Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.
Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.
| name | os-cleaner |
| description | Keep Agentic OS worktree and work-item state clean after Jira terminal statuses or merged pull requests. |
Use when the user asks to clean, audit, or reconcile Agentic OS project worktrees, stateful directories, or stale work items after Jira or GitHub lifecycle closure.
Canonical workflow: harness/shared_factory/03-workflows/engineering/os_cleanup/.
This skill is an invocation mirror for that workflow, not an independent policy
source.
worktrees/index.yml, worktrees/closed.yml when present, and active work-item lanes.03-workflows or 04-automations.Refresh cached metadata for registered worktrees:
Run:
agentic-os project work-item infer-complete --root <os-root> --dry-run
agentic-os project worktree cleanup-closed --root <os-root> --dry-run
If the active work inference decisions are correct, run:
agentic-os project work-item infer-complete --root <os-root> --apply
If the worktree dry-run candidates are correct, run:
agentic-os project worktree cleanup-closed --root <os-root> --apply
Run --remove-files when the user has asked for physical checkout removal or the automation approval record explicitly allows it. For merged-PR cleanup, dirty status is not a blocker unless REOPEN.md exists.
Run:
agentic-os project work-item finalize-lingering --root <os-root> --apply
Record inference decisions, candidate counts, closed registry path, removed merged worktrees, REOPEN.md holds, and active-container index path in the worklog or automation log.
worktrees/ directory.REOPEN.md without asking..cursor/, .claude/, .features/, watch folders, peak-styles.css, or submodule state.worktrees/closed.yml; physical deletion is not.Return: