/hooks:session-end-issue-hook

Configure a Stop hook that checks for unfinished TodoWrite todos at the end of each Claude response. If any pending or in-progress todos exist when you try to end the session, Claude is prompted to create GitHub issues for them before the conversation closes.

When to Use This Skill

Context

Detect current state:

• Settings file: !find . -path '*/.claude/settings.json' -maxdepth 3
• Existing Stop hooks: !find . -path '*/.claude/settings.json' -maxdepth 3 -exec jq -r '.hooks.Stop // empty' {} +
• gh auth: !gh auth status
• jq available: !jq --version

Parameters

Execution

Step 1: Check prerequisites

Verify that jq is installed — the hook requires it to parse the session transcript. Report if missing.

Unless --no-verify is passed: verify gh is installed and authenticated (gh auth status). Report the auth state so the user knows whether GitHub issue creation will work when the hook fires.

Check that the todo tools are enabled for the sessions this hook will run in: the hook reads TodoWrite calls from the transcript, and TodoWrite/Task* are disabled on Opus 4.8, Sonnet 5, Fable 5/5.1 and newer (Claude Code 2.1.233+) unless CLAUDE_CODE_ENABLE_TODO_TOOLS=1 is set in the session environment. If it is not set, say so and offer to add it (for example under env in .claude/settings.json) — without it the hook never fires, and that silence is not "all todos completed".

Step 2: Locate hook script

The hook script ships with the hooks-plugin. Determine its path:

• If ${CLAUDE_PLUGIN_ROOT} is set: use ${CLAUDE_PLUGIN_ROOT}/hooks/session-end-issue-hook.sh
• Otherwise: look for the script relative to this skill's location (../../hooks/session-end-issue-hook.sh)
• Last resort: ask the user for the absolute path to the installed hooks-plugin

Report the resolved path to the user.

Step 3: Configure .claude/settings.json

Read existing .claude/settings.json if it exists. Merge the Stop hook — preserve all existing configuration.

If a Stop hook pointing to session-end-issue-hook.sh already exists, report that the hook is already configured and skip to Step 4.

If other Stop hooks exist, add alongside them (both will run).

Configuration to merge under the hooks key:

{
  "Stop": [
    {
      "matcher": "*",
      "hooks": [
        {
          "type": "command",
          "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks/session-end-issue-hook.sh\"",
          "timeout": 15
        }
      ]
    }
  ]
}

Use timeout: 15 (15 seconds) — transcript parsing is fast. Create .claude/ directory if it does not exist.

Step 4: Finalize

Report a summary of what was configured, including:

• Path to the hook script
• Location of .claude/settings.json
• Whether gh auth is ready

Post-Actions

After configuring the hook:

1. Suggest committing .claude/settings.json to share the hook with the team
2. Remind the user that the hook fires at the end of every Claude response — it is silent when all todos are completed and only blocks when pending todos exist
3. If gh is not authenticated, remind the user to run gh auth login so GitHub issue creation works when the hook fires

How the Hook Works

When the hook fires at the end of a Claude response:

1. It reads the session transcript from transcript_path
2. Finds the last TodoWrite call — the final state of the todo list
3. Extracts any todos with status: "pending" or status: "in_progress"
4. If none exist → silently exits (no interruption)
5. If any exist → outputs a block decision with the list of pending todos and suggested gh issue create commands

Claude then has the opportunity to create the issues or ask the user what to do with the deferred work.

Agentic Optimizations

Quick Reference