For AI agents

ge ships artifacts for coding agents alongside its code. This page lists them, says where each lives in the repository, and points at the machine-readable copies of this documentation.

Skills

Skills are folders holding a SKILL.md (the Agent Skills format): a description that tells an agent when to use it and a body with the procedure. Install one into your agent with gh skill (any host: --agent claude-code, copilot, cursor, codex, gemini), or use the copy bundled in the wheel.

ge

Use when asked to work on a GitHub issue, PR, or discussion. Resolves flexible input (URL, folder, number), confirms with the user, prepares context, and guides the workflow.

gh skill install thorwhalen/ge ge --agent claude-code

Source: ge/data/skills/ge (bundled with the pip package).

ge-analyze

Use when you need to check whether a GitHub issue or PR is still relevant, stale, or already resolved — without preparing full context or downloading media.

gh skill install thorwhalen/ge ge-analyze --agent claude-code

Source: ge/data/skills/ge-analyze (bundled with the pip package).

ge-autonomous-execution

Behavioural policy for running unattended. Use when you have been launched in headless / auto-permission mode (e.g. by ge run-roadmap or ge run-triage) and there is no user available to answer questions. Converts every clarifying question into a logged decision so progress continues.

gh skill install thorwhalen/ge ge-autonomous-execution --agent claude-code

Source: ge/data/skills/ge-autonomous-execution (bundled with the pip package).

ge-context

Use when you need to prepare, read, or refresh full context for a GitHub issue, PR, or discussion — fetching data, downloading media, and writing structured context documents.

gh skill install thorwhalen/ge ge-context --agent claude-code

Source: ge/data/skills/ge-context (bundled with the pip package).

ge-cross-repo-triage

Triage and resolve a cross-repo issue backlog. Use when launched by ge run-triage against multiple repos — Phase A classifies and orders issues into a TriageBacklog; Phase B executes them one at a time (failing test → confirm red → fix → confirm green → open PR, then stop). Stops at PR; merging is a separate later phase.

gh skill install thorwhalen/ge ge-cross-repo-triage --agent claude-code

Source: ge/data/skills/ge-cross-repo-triage (bundled with the pip package).

ge-roadmap-execution

Execute a roadmap of tasks end-to-end using GitHub as durable memory. Use when launched against a roadmap issue (typically by ge run-roadmap) — take the next todo task, do it, verify it, mark it done, log decisions, and repeat. Survives context exhaustion because each work unit rehydrates from GitHub.

gh skill install thorwhalen/ge ge-roadmap-execution --agent claude-code

Source: ge/data/skills/ge-roadmap-execution (bundled with the pip package).

ge-write-issue

Use when AUTHORING a GitHub issue, comment, or report that a human will read — especially a non-technical stakeholder, a client, or someone outside the repo. Covers what goes in an issue versus a comment, how to layer detail so the reader can stop early, how to ask a question that actually gets answered, and how to assign it so someone is on the hook. Triggers on: ‘open an issue for’, ‘post this to the issue’, ‘ask the client’, ‘report this back’, ‘write it up as an issue’, ‘file a question’, ‘let them know’, or any request to communicate findings outward through GitHub. This is about WRITING issues; ge-analyze and ge-context are about WORKING ON issues that already exist.

gh skill install thorwhalen/ge ge-write-issue --agent claude-code

Source: ge/data/skills/ge-write-issue (bundled with the pip package).

The bundled skills are also on disk after pip install ge, under the package’s data/skills/ directory; link them into an agent without network access with skill link-skills <that directory>.

Instruction files

Files agents read before working in this repository.

Machine-readable documentation

This site publishes the same documentation in forms that fit an agent’s context window:

  • llms.txt: an index of every page with a one-line description (llms.txt format)

  • ge.md: the whole documentation as one Markdown file

  • <page>.html.md: a rendered Markdown twin of every page, advertised from each page’s <head> with <link rel="alternate" type="text/markdown">

  • objects.inv: the Sphinx inventory: a symbol-to-URL index (sphobjinv convert plain objects.inv -)