GravionLabs/elysion / .agents/skills/github-issue
github-issue
VerifiedGitHub issue conventions: types, [Level] titles, branches, commits, native sub-issues, plan-to-issue creation. Use for any GitHub issue work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
| references/conventional-commits.md | markdown | 1.9 KB |
| references/create-from-plan.md | markdown | 2.3 KB |
| references/decisions.md | markdown | 472 B |
| references/milestones.md | markdown | 2.6 KB |
| references/release-branches.md | markdown | 6.8 KB |
| references/standalone-issue.md | markdown | 2.9 KB |
| references/sub-issues.md | markdown | 4.9 KB |
references/conventional-commits.md
View on GitHub# Conventional Commits
Always use conventional commit format.
## Format
```
<type>[(<scope>)]: <description>
```
## Types
| Type | When to use |
| ---------- | ---------------------------------------- |
| `feat` | New feature or capability |
| `fix` | Bug fix |
| `docs` | Documentation only |
| `perf` | Performance improvement |
| `refactor` | Code restructure without behavior change |
| `revert` | Reverts a previous commit |
| `chore` | Maintenance, deps, housekeeping |
| `ci` | CI/CD changes |
| `style` | Formatting, whitespace |
| `test` | Test additions or fixes |
| `build` | Build system changes |
## Rules
- Imperative mood: "add feature" not "added feature"
- Lowercase type and description
- No period at the end
- Max 72 characters for subject line
- Optional scope in parentheses
## Branch Naming
`<type>/<issue-nr>-<slug>` — `<type>` is the conventional-commit type of the issue title after stripping the level prefix `^\[(Epic|Feature|PBI|Task|Bug)\] ` (case-insensitive) and the legacy `Epic: ` / `Feature: ` (`feat`, `fix`, `docs`, `refactor`, `chore`, …). Epics and Features have no commit type in their title: use `feat`. A batch over several epics: `feat/epics-<nrs>-<slug>`.
Examples: `[Bug] fix: x` → `fix/<nr>-x`, `[PBI] feat(github): y` → `feat/<nr>-y`, `feat/42-add-pr-skill`, `fix/43-pr-title`, `chore/44-update-deps`.
## Issue footer
A commit for a PBI or Bug ends with `Refs #<nr>`, not `Closes`: PRs target `release/next` (or `release/x.y`), so `Closes` would not fire there; the PR carries `Closes #<nr>`. Subject keeps `(#<nr>)`; the footer is its own last line, matched by `git log -E --grep "^Refs #<nr>$"`.
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 |