Menu
Gest Promote. Promote or sync durable Gest work with GitHub issues using gh, storing GitHub metadata back on Gest entities.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Gest Format. Run formatting, linting, typechecking, compile/static checks, and mechanical diff hygiene; fix mechanical issues. Use gte for tests and gdo for documentation.
Gest Implement. Implement one concrete Gest task end to end by reading, claiming, splitting if too broad, editing, verifying, reviewing, formatting as appropriate, and completing it.
Gest Setup. Bootstrap or refresh a Gest-tracked repository workflow surface across tool checks, project command contracts, Justfile targets, AGENTS.md mappings, docs, tests, and setup follow-ups.
Gest Test. Run unit, API regression, smoke, regression, and integration tests appropriate to the changed code; add missing tests when the task changes callable behavior.
Gest Track Work. Use for substantial coding, debugging, implementation, refactoring, documentation, verification, GitHub issue planning, or project work. GTW is the router that classifies requests, chooses/creates Gest outline parents, creates session or development tasks, decides whether a spec or parallel work is needed, and routes to the g* stage skills.
Gest Brainstorm. Explore rough ideas or ambiguous requests, inspect existing code/docs/Gest context, ask clarifying questions when needed, and decide whether to create a spec, outline issue, plan, or session task.
| name | gpr |
| description | Gest Promote. Promote or sync durable Gest work with GitHub issues using gh, storing GitHub metadata back on Gest entities. |
Use when work should become externally visible on GitHub.
Promote durable user-visible, architecture-relevant, multi-session, release-worthy, or externally trackable work. Do not promote every leaf task.
For every development depth-1 parent and every development iteration close, an
explicit gpr decision is required. Either create/sync the GitHub issue and
store metadata, or record why the work is staying local. Do not silently skip
GitHub issue integration for development work.
gh issue create or gh issue edit, unless the
user has already agreed to GitHub issue integration for this workflow scope.gest task meta set <id> github.issue <number>
gest task meta set <id> github.url <url>
gest task tag <id> github
Also attach metadata to the development iteration when applicable.
When promoting work to GitHub, include public-safe tag classification context from references/tag_dependency_workflow.md when it helps reviewers understand scope. Do not expose private Gest IDs unless the target repo policy allows them.