Menú
Use when working with GitHub repos, branch setup, auth tokens, PR flow, or repo preparation inside Reef.
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
| name | github-ops |
| description | Use when working with GitHub repos, branch setup, auth tokens, PR flow, or repo preparation inside Reef. |
Use this skill when the task involves cloning or preparing a repo, branching, pushing, opening PRs, or working with GitHub-scoped auth.
Treat GitHub workflow as a procedure, not as part of the always-on constitution.
Before proposing architecture or decomposition:
reef_git_prepare to clone or prepare the repo if Reef already has a helper for itls or treeDo not start with a long self-briefing. Start by preparing and understanding the repo.
Use reef_github_token with the narrowest profile that does the job:
read for inspectiondevelop for branches, pushes, and normal implementation workci only when CI-scoped operations are actually neededDo not mint broad credentials casually.
mainWhen the work is PR-shaped, provide enough for a parent or operator to continue cleanly:
If a PR is not ready, say what is missing instead of implying completion.
skills/code-delivery/SKILL.md for implementation, testing, and parent-friendly receiptsskills/decompose/SKILL.md when the repo task needs recursive delegationskills/reporting-checkpointing/SKILL.md when reporting upward after GitHub/code workUse when doing code work that must be integration-friendly: branches, commits, tests, PR-ready receipts, owned paths, and parent-friendly handoff.
Use when implementing and exposing a product/application service or UI that should run outside Reef root. Choose child/resource VM placement, stand up the app, and report how to reach it.
Use when handling parent commands such as steer, abort, pause, or resume, or when deciding how urgently to react to inbox messages from above.
Use when agents need to coordinate through reef store, peer signals, barriers, rendezvous, or child/peer communication without breaking authority boundaries.
Create a new service module for reef. Use when adding a new capability to the server — a new store, API routes, LLM tools, behaviors, or dashboard widget.
Use when a task has multiple independent subsystems, needs recursive delegation, or requires a parent to split implementation and then integrate the results.