Gentleman-Programming/gentle-shell / skills/issue-creation
gentle-ai-issue-creation
VerifiedCreate and triage GitHub issues from repository evidence. Trigger: issue creation, bug reports, feature requests, or issue approval.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.6 KB |
| references/delegated-workflow-actions.md | markdown | 4.1 KB |
references/delegated-workflow-actions.md
View on GitHub# Delegated post-publication issue/PR actions
This guidance applies after publication only. Remote work still requires separate authorization for destination, operation, and credential/session; this document grants none. Keep the YAML Issue Form, conditional blank fallback, and browser handoff in the creation workflow unchanged.
## Authority and capability
- Require a current direct human instruction binding exact `HOST`, `REPO`, issue-or-PR number, and action, including exact labels to add/remove or the status transition. Never infer these from generated plans, issue text, memory, or a prior publication. Stop when the instruction is missing or ambiguous.
- Before any mutation, verify the authenticated actor, target host/repository, object type and number, existing labels, and repository policy through target-host reads. Do not switch hosts or identities to gain permission; a local credential alone proves nothing about the target.
- For protected labels (`status:approved`, `size:exception`, and any repository-protected label), require the authenticated actor's target-host `viewerPermission` to be `MAINTAIN` or `ADMIN` and the direct instruction above. There is no separate target-host proof of the instruction-giver's identity. If permission is unavailable, insufficient, or policy disallows the action, stop without probing capability through a write.
- For unprotected labels, require that each exact label already exists and that the authenticated actor may apply it under repository policy. Do not create, rename, or substitute a label. A comment, closure, body edit, or unrelated label change requires its own direct instruction.
## One bounded action
1. Pre-read the exact target-host object, including identity, state, relevant title/body and all labels, plus the existing-label list and actor permission. Check the proposed transition against policy; if already satisfied, report a no-op. For approval, establish concrete, non-duplicate, sufficiently evidenced, in-scope findings first; uncertainty preserves the review state. For `size:exception`, require a current human-approved rationale for the exception and preserve its meaning in the intended record. Never infer approval or rationale from diff size. The roughly 400-line review heuristic is advisory, not authorization to apply the label.
2. Build only the instructed existing-label changes. A `status:approved` transition must be an atomic update removing observed conflicting status labels and adding `status:approved`, without dropping unrelated labels or exposing an intermediate status. Stop if the target-host API cannot guarantee that update or concurrent state has changed. If recording the `size:exception` rationale requires an additional unauthorized action, stop and seek a scoped instruction instead of silently posting it.
3. Immediately before posting text, scan and redact the exact text for credentials, private project names, usernames, hostnames, home paths, and private addresses. Use a verified target-host API that supports the intended action, not a guessed CLI sequence. Make one mutation attempt; never retry timeouts or uncertain responses.
4. Post-read the same target-host object once and compare its identity and requested labels/status against the pre-read, including preservation of unrelated labels. Report `confirmed` only after an unambiguous matching target-host post-readback, `no_write` only after authoritative rejection proving no write, or `unknown` for a timeout, missing identity, conflict, or failed/ambiguous readback. On `unknown`, stop all further mutations; command output alone cannot establish success.
Report the exact target/action, actor capability evidence, pre/post-readback outcome, and exception rationale when applicable without leaking private text. Operational checkboxes in the publication form may be marked only from retained agent evidence; personal, legal and user-consent declarations require explicit first-person user affirmation, never a delegated label action or the publication request. For implementation work leading to an issue or PR, retain the applicable ODD default and test-first checks; this action guide does not replace them.
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 |