Resolve GitHub issues

Use this skill for an explicit request to implement a tracked issue. Start with read-only issue, branch, worktree, and repository-guidance checks; confirm the issue's acceptance criteria and dependencies before changing files.

Create or reuse an isolated worktree under .agents/worktrees/ and a branch that identifies the issue (fix/<number>-<slug>, feat/<number>-<slug>, or refactor/<number>-<slug>). Read workflow-details.md for naming/reuse rules; read repository-templates.md only when repository templates or contributing rules are present. Implement with a real RED → GREEN → REFACTOR loop and run the relevant checks described in quality-validation.md. Map every explicit acceptance criterion to an automated test, including boundary behavior the fix must preserve. A manual assertion supplements this coverage; it does not replace a regression test. In RED, the bug test must fail for the reported reason while already-correct boundary tests may pass. Read commit-standards.md when making commits, and examples.md when a concrete commit message model is needed.