GitHub Issue Authoring
Repository continuity composition
For repository-scoped work, compose maintain-repository-continuity in
Resume mode before selecting work. This skill is continuity read-only: do
not create, refresh, or otherwise mutate CONTINUITY.md unless a separate
authorized repository-changing workflow takes ownership of that handoff.
- Contribute: Verified repository context, issue dependencies, scope, acceptance criteria, and evidence gaps
- Never claim: That an issue was created or updated without live evidence, or authority to mutate CONTINUITY.md without separate authorization
Purpose
Transform repository evidence into a clear GitHub issue that another engineer or
agent can execute without guessing scope, constraints, or validation.
Required Inputs
Resolve as much of the following as possible:
- problem statement, desired outcome, and user motivation
- relevant specifications, audits, notes, or defect evidence
- affected systems, constraints, exclusions, and dependencies
- repository conventions, templates, labels, and validation commands
- unresolved questions or decisions that must stay visible
When repository evidence is incomplete, label assumptions explicitly.
Workflow
extract the durable problem, goal, boundaries, and observable outcome
inspect repository evidence before prescribing paths, commands, or ownership
choose whether the result should be one issue or an ordered batch of issues;
if scoped instructions select the Ego Hygiene issue-title policy, follow
canonical issue titles before drafting
the title or proposing labels
write copy-ready issue content using the focused resources:
./references/copy-ready-checklist.md
./templates/GITHUB_ISSUE.template.md
make acceptance criteria observable and keep non-goals explicit
preserve the user's copy-and-paste formatting preference; when fenced blocks would break copying or rendering, use four-space-indented inner code examples instead
validate title clarity, internal consistency, dependency order, and execution readiness;
report contract provenance, proposed versus actual validation, and provider
label availability separately when the title policy applies
Constraints
- Do not implement the requested work inside the issue-authoring step.
- Do not invent repository paths, commands, labels, or ownership.
- Do not mix multiple independently shippable outcomes into one issue without stating why.
- Do not hide unresolved decisions or missing evidence.
- Do not embed provider-specific tooling instructions into the core workflow.
- Do not expand a read-only role's tools to run a formatter or validator. Use an
already authorized executor or mark local validation unavailable.
Completion Criteria
Provenance
This canonical skill is first-party Ego Hygiene content curated from the staged
candidate at .staging/skills/github-issue-authoring/SKILL.md.
Source Delta
- Adopted: the staged workflow for extracting durable intent, inspecting the
repository before prescribing work, and validating issue completeness.
- Rewritten: canonical metadata, copy-ready template, deterministic evals, and
the explicit formatting rule for four-space-indented inner code examples when
fenced blocks would copy poorly.
- Rejected: the placeholder
github-issue staging copy as a synonym identity;
broader or specialized legacy variants such as github-issues and
create-github-issue-* were reviewed as overlap but not adopted into the core
provider-neutral workflow.
1---2name: github-issue-authoring3description: Converts evidence, specifications, audits, bug reports, and rough notes into scoped, copy-ready GitHub issues or dependency-aware issue batches. Use when defining implementation work clearly without performing the implementation itself.4license: MIT5metadata:6 source: https://skillmd.com/skills/egohygiene/github-issue-authoring7 aether-version: "1.2.0"8 aether-status: "experimental"9 aether-scope: "organization"10 aether-domain: "authoring"11 aether-owners: "egohygiene"12 aether-created: "2026-08-08"13 aether-updated: "2026-10-03"14 aether-executable-resources:15 - "scripts/verify_title_contract.py"16---1718# GitHub Issue Authoring1920<!-- aether-continuity-disposition: reader -->2122## Repository continuity composition2324For repository-scoped work, compose `maintain-repository-continuity` in25**Resume** mode before selecting work. This skill is continuity read-only: do26not create, refresh, or otherwise mutate `CONTINUITY.md` unless a separate27authorized repository-changing workflow takes ownership of that handoff.2829- **Contribute:** Verified repository context, issue dependencies, scope, acceptance criteria, and evidence gaps30- **Never claim:** That an issue was created or updated without live evidence, or authority to mutate CONTINUITY.md without separate authorization3132## Purpose3334Transform repository evidence into a clear GitHub issue that another engineer or35agent can execute without guessing scope, constraints, or validation.3637## Required Inputs3839Resolve as much of the following as possible:4041- problem statement, desired outcome, and user motivation42- relevant specifications, audits, notes, or defect evidence43- affected systems, constraints, exclusions, and dependencies44- repository conventions, templates, labels, and validation commands45- unresolved questions or decisions that must stay visible4647When repository evidence is incomplete, label assumptions explicitly.4849## Workflow50511. extract the durable problem, goal, boundaries, and observable outcome522. inspect repository evidence before prescribing paths, commands, or ownership533. choose whether the result should be one issue or an ordered batch of issues;54 if scoped instructions select the Ego Hygiene issue-title policy, follow55 [canonical issue titles](references/canonical-issue-titles.md) before drafting56 the title or proposing labels574. write copy-ready issue content using the focused resources:5859 - `./references/copy-ready-checklist.md`60 - `./templates/GITHUB_ISSUE.template.md`61625. make acceptance criteria observable and keep non-goals explicit636. preserve the user's copy-and-paste formatting preference; when fenced blocks would break copying or rendering, use four-space-indented inner code examples instead647. validate title clarity, internal consistency, dependency order, and execution readiness;65 report contract provenance, proposed versus actual validation, and provider66 label availability separately when the title policy applies6768## Constraints6970- Do not implement the requested work inside the issue-authoring step.71- Do not invent repository paths, commands, labels, or ownership.72- Do not mix multiple independently shippable outcomes into one issue without stating why.73- Do not hide unresolved decisions or missing evidence.74- Do not embed provider-specific tooling instructions into the core workflow.75- Do not expand a read-only role's tools to run a formatter or validator. Use an76 already authorized executor or mark local validation unavailable.7778## Completion Criteria7980- [ ] The issue can be executed without reopening accepted decisions.81- [ ] Scope, non-goals, and dependencies are explicit.82- [ ] Validation steps are observable and repository-aware.83- [ ] Copy-ready formatting is preserved.84- [ ] Missing evidence and open questions remain visible.85- [ ] Selected title policy is discovered explicitly; missing sources, tools,86 classification, or live label evidence are not reported as conformance.8788## Provenance8990This canonical skill is first-party Ego Hygiene content curated from the staged91candidate at `.staging/skills/github-issue-authoring/SKILL.md`.9293## Source Delta9495- Adopted: the staged workflow for extracting durable intent, inspecting the96 repository before prescribing work, and validating issue completeness.97- Rewritten: canonical metadata, copy-ready template, deterministic evals, and98 the explicit formatting rule for four-space-indented inner code examples when99 fenced blocks would copy poorly.100- Rejected: the placeholder `github-issue` staging copy as a synonym identity;101 broader or specialized legacy variants such as `github-issues` and102 `create-github-issue-*` were reviewed as overlap but not adopted into the core103 provider-neutral workflow.