octoperator

This skill provides the source-of-truth GitHub conventions, the gh CLI cookbook, and the settings schema that every Octoperator action consults. It should be loaded whenever Octoperator turns a request into GitHub artifacts — when the user asks to "plan an epic", "create an issue", "implement an issue", "review a PR", or "sync project status", or otherwise works with GitHub epics, issues, sub-issues, milestones, branches, pull requests, reviews, or Projects v2 board updates. It is the shared knowledge layer, not a substitute for the action skills that perform the writes.

This skill should be used when the user asks to "implement issue

This skill should be used when the user asks "what should we build next", "research improvements for this repo", "propose new features", "what should we refactor", "find tech debt", "what's missing in this project", "find things to improve", or invokes /octoperator:research. Analyzes the repository and produces a ranked list of proposed work across new features, refactoring, tech debt, test coverage, docs, and DX — not just new features — optionally filing them as GitHub issues.

This skill should be used when the user asks to "run autopilot", "keep shipping until there's nothing left", "drain the ready issues automatically", "autopilot this repo", or invokes /octoperator:autopilot. Bounded orchestrator that loops over the lifecycle — discover work, run auto (implement -> review -> merge), and when no work remains, research proposes more.

This skill should be used when the user asks to "auto-ship issue

This skill should be used when the user asks to "set up octoperator", "configure octoperator", "octoperator setup", "bootstrap octoperator settings", "initialize the project board", "create the octoperator config", or invokes /octoperator:setup. Detects the repo, probes whether the token can access Projects v2, optionally selects or creates a board, and writes .claude/octoperator.local.md. Projects is treated as optional and auto-detected.

This skill should be used when the user asks to "create an issue", "open an issue for X", "file a bug", "log a task", "make a ticket", or invokes /octoperator:issue. Turns one natural-language request into a single well-formed GitHub issue with type/priority labels, acceptance criteria, milestone, and a project board item.

This skill should be used when the user asks to "plan an epic", "break this down into issues", "decompose this into issues", "create an epic for X", "turn this request into a backlog", or invokes /octoperator:plan-epic. Decomposes a large natural-language request into a GitHub epic issue plus linked child issues, milestone, labels, and project board items.

This skill should be used when the user asks to "review PR

This skill should be used when the user asks to "sync status", "show project status", "give me a standup", "what's the status of the project", "reconcile the board", or invokes /octoperator:sync. Produces a standup-style status report from issues, PRs, milestones, and the Projects v2 board, and auto-reconciles detected drift.