---
description: Read a GitHub issue, scope it, implement it with the right agent, and offer to close it.
argument-hint: <issue number, e.g. 68>
---

Work on GitHub issue **#$ARGUMENTS** on the repo `mourad-b/event-unified`.

The GitHub remote is named `gh` (not `origin` — `origin` is Bitbucket). All issue operations target GitHub.

Steps:
1. **Read it:** `gh issue view $ARGUMENTS` (add `--comments` if there's discussion). Summarize the ask in one line. If the issue is vague (e.g. a broad "module" ticket), propose splitting it into sub-issues before coding — ask before creating them.
2. **Scope:** which subdomain (frontend/backend) and which instance(s)? Use the issue's labels (client/type/priority) as hints. Ask one question only if genuinely ambiguous.
3. **Delegate** to the matching agent based on the type:
   - `bug` → `bug-investigator`  |  `feature` → `laravel-feature` (or `livewire-expert`)
   - `import`/`export` → `excel-io`  |  instance-specific → `multi-instance`
   - always finish with a test from `test-writer`.
4. **Quality gate:** run the `/pre-commit` checks (pint, php -l, tests, mini security review, CLAUDE.md sync).
5. **Link & close:** when done and verified, suggest a commit message ending with `Fixes #$ARGUMENTS`, and offer to add a closing comment summarizing the fix via `gh issue comment` / close via the merged commit. **Do not commit or close the issue without explicit approval.**

Report: what the issue asked, files changed, test result, and the proposed commit message.