issue

星标6

分支1

更新时间2026年4月11日 09:09

Create a GitHub issue with structured sections for a feature, bug fix, or crash

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

haterade22

haterade22/LOTRAOM

打开 GitHub 仓库查看创作者相关仓库

下载

GitHub Issue Creator

Create a structured GitHub issue for: $ARGUMENTS

Step 1: Parse Arguments

First word = type (bug, feature, crash). Rest = description.

Step 2: Gather Context

git log --oneline -5, git diff --name-only, CHANGELOG.md [Unreleased] section.

Step 3: Create Issue

Bug/Crash:

gh issue create --title "<type>: <description>" --label "<type>" --body "$(cat <<'EOF'
## Problem
[Error, symptoms, reproduction steps]

## Analysis
[Root cause, which module/feature affected]
[Decompiled TaleWorlds class if Harmony/GameModel related]

## Solution
[Changes and rationale]

## Files Changed
- `path/file.cs` — description

## Testing
[How verified — unit tests, manual testing]
EOF
)"

Feature:

gh issue create --title "feat: <description>" --label "feature" --body "$(cat <<'EOF'
## Motivation
[Problem solved, which system benefits]

## Design
[Architecture: entry points, services, adapters, GameModels]
[ADR reference if applicable]

## Implementation
[Key files, patterns used, DryIoC registration]

## Testing
[Coverage, verification approach]
EOF
)"

Important

Label: bug, feature, crash, enhancement, launcher, devops
Close with gh issue close <number> when complete

同仓库更多 Skills

同仓库

context-budget

haterade22/LOTRAOM

Audit context window consumption across LOTRAOM agents, skills, rules, MCP servers, and CLAUDE.md. Report token estimates, flag bloat, recommend trims.

2026-05-186

freeze

haterade22/LOTRAOM

Hard-block Edit/Write outside a chosen directory. Use to scope-lock edits during a focused fix or refactor. Pair with /unfreeze to release.

2026-05-186

investigate

haterade22/LOTRAOM

Six-phase root-cause debugging for crashes, build failures, or "why is this broken" reports. Iron Law - no fixes without root cause. Auto-engages /freeze.

2026-05-186

unfreeze

haterade22/LOTRAOM

Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.

2026-05-186

codex-verify

haterade22/LOTRAOM

Dispatch an independent Codex verification job for the current changes

2026-04-116

commit-split

haterade22/LOTRAOM

Inspect all changed files, group by logical concern, and guide atomic per-concern commits

2026-04-116

name	issue
description	Create a GitHub issue with structured sections for a feature, bug fix, or crash
argument-hint	[bug\|feature\|crash] [brief description]

GitHub Issue Creator

Create a structured GitHub issue for: $ARGUMENTS

Step 1: Parse Arguments

First word = type (bug, feature, crash). Rest = description.

Step 2: Gather Context

git log --oneline -5, git diff --name-only, CHANGELOG.md [Unreleased] section.

Step 3: Create Issue

Bug/Crash:

gh issue create --title "<type>: <description>" --label "<type>" --body "$(cat <<'EOF'
## Problem
[Error, symptoms, reproduction steps]

## Analysis
[Root cause, which module/feature affected]
[Decompiled TaleWorlds class if Harmony/GameModel related]

## Solution
[Changes and rationale]

## Files Changed
- `path/file.cs` — description

## Testing
[How verified — unit tests, manual testing]
EOF
)"

Feature:

gh issue create --title "feat: <description>" --label "feature" --body "$(cat <<'EOF'
## Motivation
[Problem solved, which system benefits]

## Design
[Architecture: entry points, services, adapters, GameModels]
[ADR reference if applicable]

## Implementation
[Key files, patterns used, DryIoC registration]

## Testing
[Coverage, verification approach]
EOF
)"

Important

Label: bug, feature, crash, enhancement, launcher, devops
Close with gh issue close <number> when complete