| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 27.6 KB |
| agents/reviewer-architecture.md | markdown | 2.3 KB |
| agents/reviewer-security.md | markdown | 2.6 KB |
| references/durable-context.md | markdown | 2.0 KB |
| references/incident-ledger.md | markdown | 3.5 KB |
| references/mode-audit.md | markdown | 2.9 KB |
| references/mode-ship.md | markdown | 8.6 KB |
| references/mode-triage.md | markdown | 6.0 KB |
| references/persona-catalog.md | markdown | 3.3 KB |
| references/project-context.md | markdown | 7.7 KB |
| references/public-reply.md | markdown | 1.7 KB |
| references/release-surfaces.md | markdown | 3.6 KB |
| references/review-patterns.md | markdown | 7.5 KB |
| scripts/audit_signals.py | script | 25.4 KB |
| scripts/incident_ledger.py | script | 12.8 KB |
| scripts/release_gate.py | script | 14.2 KB |
| scripts/run-tests.sh | script | 639 B |
references/public-reply.md
View on GitHub# Public Reply Mechanics (maintainer, issue or PR)
Used by Triage Mode and Ship / Release Follow-through for the actions around a reply. The reply body belongs to `/write` Public Reply Mode; without `/write`, open with `@<login>` and at most one short thanks, match the opener's language, and give one or two sentences naming the exact ship state and the reporter's next step, each true at the moment of posting. `AGENTS.md` or `CLAUDE.md` in the target repo overrides this shape.
1. Resolve `@<login>` from `gh issue view` / `gh pr view --json author` before posting, and re-read the live item there rather than replying from memory. When requesting logs, crash dumps, screenshots, or local-state archives, ask only for the minimum non-sensitive public facts; use a private support channel only when the project's public context provides one. Choose a next step the reporter can perform with the reported failure or accessibility constraint still present; do not require disabling the assistive capability they need to follow it. This applies even when `/write` is unavailable.
2. Edit your own comment in place (`PATCH /repos/{owner}/{repo}/issues/comments/{comment_id}`) only while nobody has replied after it. Once the reporter or anyone else has replied, post a new comment instead of rewriting history; never delete and repost unless the old text must disappear.
3. After posting or editing, re-read the comment body, author, target item, and issue/PR state. The public action is not complete without that receipt.
4. Close only when the fix is shipped, already available in the latest release, the report is invalid, the report is a duplicate, or the maintainer explicitly asked for closure. Otherwise leave it open with the next-release acknowledgement.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |