Respond To Issue
Description
Respond to an issue triggered by `@elixpoo` mention or the `ELIXPO` label. ## Step 1 — Load context - Read `.elixpo-context/context.md` ONCE. Don't `ls`/`find`/`tree` to rediscover what's there. - `gh issue view <n> --comments` ONCE. Don't repeat with different `--json` flags. - Do NOT re-read README.md or CLAUDE.md unless the context snippet is truncated. ## Step 2 — Classify the request Look at what the user actually asked. Pick ONE: - **QUESTION / DISCUSSION / LGTM** — user wants an answ
Installation
Installs to ~/.claude/commands/elixpo-claudeops.elixpo-respond-to-issue.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/elixpo/claudeOps.elixpo/HEAD/.claude/commands/respond-to-issue.md -o ~/.claude/commands/elixpo-claudeops.elixpo-respond-to-issue.md Restart Claude Code, or start a new session, for it to be picked up.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Awesome Go
A curated list of awesome Go frameworks, libraries and software
Development next.js
| The React Framework | 138360 | 1503 | 1 |
Development sharing-skills
skill for guidance.
Development root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger.
Development Template Skill
Minimal skeleton for a new skill project structure.
Development Third-party Notices
THE FOLLOWING SETS FORTH ATTRIBUTION NOTICES FOR THIRD PARTY SOFTWARE THAT MAY BE CONTAINED IN PORTIONS OF THI
Development