Keeps a project's to-do list and memory in GitHub issues — files each finding (from a review, an audit, or the user) as its own issue without duplicates, lists the open issues that bear on the current work, and closes an issue with a comment recording what was wrong, what was tried, what worked, and how it was fixed. Use when review findings or a list of problems should become tracked work (a paper's misleading claims, a codebase's bugs, improvements for later), when starting or resuming work and deciding what to do next, or when a fix has landed and its issue should be closed with a record. N
A source-grounded starter task has not been verified for this skill yet.
SKILL.md
name: issuesdescription: Keeps a project's to-do list and memory in GitHub issues — files each finding (from a review, an audit, or the user) as its own issue without duplicates, lists the open issues that bear on the current work, and closes an issue with a comment recording what was wrong, what was tried, what worked, and how it was fixed. Use when review findings or a list of problems should become tracked work (a paper's misleading claims, a codebase's bugs, improvements for later), when starting or resuming work and deciding what to do next, or when a fix has landed and its issue should be closed with a record. Needs the GitHub CLI; warns before posting to a public repository.
issues
This skill's instructions live in .claude/skills/issues/SKILL.md.
Read that file now and follow it, with the files it points to. Read AGENTS.md
first if you have not already.
It was written for Claude Code. Running it from Codex, Antigravity or another agent:
Arguments. Where it says $ARGUMENTS, use what the user asked for.
Claude Code agents. Where a step hands work to an agent in .claude/agents/ (through the
Agent or Task tool), do that step where it appears in the procedure: never later, and never
skip it. A step that gates what follows still gates it (/commit runs its verifier before it
commits). Read the agent's file for what the step checks.
Fresh context. If the step needs a context that has not seen your work, for example a claim
verifier that must never see the draft, run it in a separate session or worker that has not
seen the draft, if your tool can start one, and give it only what the step says to pass. If it
cannot, do the step yourself, mark every result it produced not independently verified, and
tell the user to repeat that check in Claude Code (/verify-claims for citations) before
relying on it.
Claude Code settings.allowed-tools, model, effort, argument-hint and
disable-model-invocation in the source's frontmatter configure Claude Code. Ignore them.
Guards. Claude Code's guard hooks do not run for you. Follow the rules in AGENTS.md
yourself; the git pre-commit gate and CI still apply to your commits.