# Issues

Keeps a project's to-do list and memory in GitHub issues, files each finding (from a...

- Repository: https://github.com/pedrohcgs/claude-code-my-workflow (1676 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-09-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add pedrohcgs/claude-code-my-workflow --skill issues -g -a claude-code -y`
Codex: `npx skills add pedrohcgs/claude-code-my-workflow --skill issues -g -a codex -y`
Cursor: `npx skills add pedrohcgs/claude-code-my-workflow --skill issues -g -a cursor -y`
Gemini CLI: `npx skills add pedrohcgs/claude-code-my-workflow --skill issues -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /issues, the project's to-do list and memory, in GitHub issues

Every problem worth fixing becomes an issue: a claim in the paper that misleads, a table that
disagrees with the code, a bug, an improvement for later. The open issues are the to-do list.
When a fix lands, the issue is closed with a comment that says what was wrong, what was tried, including what did **not** work, and how it was fixed. Read back months later, the closed
issues are the project's memory: auditable, searchable, and the same on every machine and for
every co-author, which a chat transcript or a local notes file is not.

This skill makes the habit cheap. It never posts anything without showing the draft first and
getting a yes.

## When to use

- **After a review**, `/review-paper`, `/seven-pass-review`, `/adjudicate-review`, or findings
  you list yourself, to turn each confirmed problem into its own issue.
- **When starting or resuming work**, to see what is open for the paper, section or files at
  hand, and pick the next thing.
- **When a fix has landed**, to close its issue with a record of what happened.

## Modes

### `file <report|text>`, turn findings into issues

The input is a findings JSON from the review runtime, a review report, or problems described in
the conversation.

The rest: https://github.com/pedrohcgs/claude-code-my-workflow/blob/HEAD/.claude/skills/issues/SKILL.md