Menü
Create a GitHub issue with structured sections for a feature, bug fix, or crash
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Audit context window consumption across LOTRAOM agents, skills, rules, MCP servers, and CLAUDE.md. Report token estimates, flag bloat, recommend trims.
Hard-block Edit/Write outside a chosen directory. Use to scope-lock edits during a focused fix or refactor. Pair with /unfreeze to release.
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.
Release the directory edit lock set by /freeze. Edit and Write are unrestricted again. No-op if /freeze was never set.
Dispatch an independent Codex verification job for the current changes
Inspect all changed files, group by logical concern, and guide atomic per-concern commits
| name | issue |
| description | Create a GitHub issue with structured sections for a feature, bug fix, or crash |
| argument-hint | [bug|feature|crash] [brief description] |
Create a structured GitHub issue for: $ARGUMENTS
First word = type (bug, feature, crash). Rest = description.
git log --oneline -5, git diff --name-only, CHANGELOG.md [Unreleased] section.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
)"
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
)"
bug, feature, crash, enhancement, launcher, devopsgh issue close <number> when complete