/ghi-author¶
Author a GitHub Issue (GHI) when a finding needs an independent work order or disposition.
Purpose¶
Produces a GHI with observed evidence, canonical intent, a failure mechanism,
and a bounded closure contract. The contract names the relevant states and
consumers, required outcomes, verification, and exit condition so the downstream
/ghi-close pass can finish without repeatedly rediscovering
its scope. Proposed implementations remain hypotheses, not acceptance criteria.
When to Use¶
Use /ghi-author for independent infrastructure defects, post-acceptance
defects, investigations needing their own home, or an explicit operator request
for an issue. Pair with /ghi-close downstream.
Corrections necessary to satisfy an active, operator-initiated OBPI stay in
that OBPI's Evidence → Change Log. Weak tests, implementation adjustments,
and evidence repairs do not need a new issue or fresh initiation. Preserve
finding identities and proof/closure references. Real boundary amendments
retain the existing operator ruling; filing an issue never discharges an
unmet obligation. See defect-fix routing.
What to Expect¶
The skill checks prior issues and brief ownership, gathers evidence, drafts
the closure contract, and creates the issue through gh. Output includes the
issue URL and routing disposition. Existing operator authorization governs;
uncertain policy or ownership conflicts with another live brief require a ruling. An investigation
names a bounded question and evidence deliverable without inventing its cause.
Independent discoveries are tracked without automatically becoming additional implementation work. Evidence that invalidates the active repair's contract must be addressed under that contract; optional neighboring improvements do not prevent a valid close.
When invoked for authoring only or to capture an independent discovery, the skill records the issue's eligibility and next-work disposition, then returns. It does not execute the finding or create planned artifacts as a side effect. An eligible but unselected issue needs no invented technical blocker.
Invocation¶
| Argument / Flag | Required | Description |
|---|---|---|
| None | — | Supply the finding and its evidence in the conversation |
Supporting Files¶
| File | Role | Read/Write |
|---|---|---|
.claude/skills/ghi-author/SKILL.md |
Agent execution instructions | Read |
.claude/rules/gh-cli.md |
gh CLI guardrails |
Read |
Related Skills and Commands¶
| Related | Relationship |
|---|---|
/ghi-close |
Downstream resolution + close pass |
gh issue create |
CLI the skill wraps |