{"slug":"issue","title":"issue","summary":"Use GitHub issues as persistent cross-session resolution memory. Create, update, and re-read issues that are self-contained and re-readable cold, recording the hypothesis and the resolution. Triggers on \"track this in an issue\", \"create an issue I can resume\", \"resume issue\", \"is","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-08-24T17:04:35.682649Z","repo":{"url":"https://github.com/mirkobozzetto/arsenal","stars":17,"forks":1,"license":"MIT","updatedAt":"2026-09-25T09:56:13Z"},"bodyHtml":"
\n

name: issue\ndescription: Use GitHub issues as persistent cross-session resolution memory. Create, update, and re-read issues that are self-contained and re-readable cold, recording the hypothesis and the resolution. Triggers on \"track this in an issue\", \"create an issue I can resume\", \"resume issue\", \"issue memory\", \"log this problem as an issue\", or when work must survive a context reset via the GitHub tracker. NOT for ephemeral session snapshots (use remember) and NOT for the manual Obsidian vault (use brain). GitHub-native, auto-re-readable on resume.\nargument-hint: \"[create|update|resume|list] [#N |

\n

issue: GitHub issues as resolution memory

\n

Persist problem-solving state in GitHub issues so a later session (or a fresh context) can re-read an issue cold and continue. Each issue records the problem, a self-contained Pickup Directive, the working hypothesis, attempts, and the final resolution.

\n

Prerequisites

\n\n

Natural-language routing

\n

Interpret intent and route:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
User saysAction
\"track this in an issue\", \"log this problem\", \"open an issue for this\"create
\"update the issue\", \"note progress on #N\", \"I found the cause\"update
\"resume issue #N\", \"what was I doing on #N\", \"pick up where I left off\"resume
\"list my memory issues\", \"what issues am I tracking\"list
\n

Default when ambiguous and a number is present → resume #N; otherwise → create.

\n

create

\n
    \n
  1. Draft the issue body from references/issue-template.md (Problem / Pickup Directive / Hypothesis / Attempts / Resolution). Fill Problem + Pickup Directive + initial Hypothesis from the current context; leave Attempts/Resolution as stubs.
    2. \n
  2. Confirm with the user before opening (opening an issue is outward-facing). Show the drafted title + body.
    3. \n
  3. Create with the memory label so resume/list can filter:\n
    gh issue create --title \"<concise title>\" --label claude-memory --body \"<rendered template>\"\n
    \nIf the label does not exist, create it once: gh label create claude-memory --description \"Claude resolution memory\" --color BFD4F2.
    4. \n
  4. Report the issue number + URL.
    5. \n
\n

update

\n
    \n
  1. Read before write: gh issue view <N> --comments to load current state.
    2. \n
  2. Append progress as a comment (never overwrite the original body):\n
    gh issue comment <N> --body \"<progress / revised hypothesis / new attempt>\"\n
    \n
    3. \n
  3. When solved, append the resolution and close (confirm before closing):\n
    gh issue comment <N> --body \"Resolution: <what fixed it and why>\"\ngh issue close <N> --reason completed\n
    \n
    4. \n
\n

resume

\n
    \n
  1. Load the issue cold:\n
    gh issue view <N> --comments\n
    \nIf no number given: gh issue list --label claude-memory --state open and ask which.
    2. \n
  2. Reconstruct context strictly from the Pickup Directive + Hypothesis + latest comments. Do not assume prior chat memory.
    3. \n
  3. State the recovered context back to the user, then continue the work.
    4. \n
\n

list

\n
gh issue list --label claude-memory --state open\n
\n

Show number, title, and updated time.

\n

Issue body template

\n

The structure lives in references/issue-template.md. Read it before create so every issue is self-contained and re-readable cold. The Pickup Directive is mandatory: it is what makes the issue resumable without prior context.

\n

Guardrails

\n\n

Delimitation

\n\n","files":[{"path":"references/issue-template.md","sizeBytes":1466,"isText":true},{"path":"SKILL.md","sizeBytes":3051,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-27T19:37:26.424152Z","sha256":"6A6FF0A4AE52DE3CA2BAD169D3384E52A50D8E08DFDDF5A6395D8F6F661C46F8","sizeBytes":2608},"review":null,"source":{"repositoryUrl":"https://github.com/mirkobozzetto/arsenal","path":"plugins/issue/skills/issue","license":"MIT","commit":"d4054b7c49d9c3e29378ba77a59140d11095aecc","subtreeSha":"23272CB0990293EA623E4D115D21A6947AE50E579C2B58557172EA44C28D030C","lastSyncedAt":"2026-09-27T19:34:26.495601Z"},"reviewedAt":"2026-09-27T19:43:11.494028Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/mirkobozzetto/arsenal/tree/main/plugins/issue/skills/issue"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install mirkobozzetto-arsenal@llmmart"},{"target":"git","command":"git clone https://github.com/mirkobozzetto/arsenal.git"}]}