Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From openpaper
Creates structured GitHub issues from session reflections or improvement ideas using the gh CLI. Bridges the gap between noticing a problem and tracking a fix.
npx claudepluginhub falense/openpaperHow this skill is triggered — by the user, by Claude, or both
Slash command
/openpaper:improveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn session insights into a trackable GitHub issue. This skill bridges the gap
Analyzes codebase impact for a given request and creates structured GitHub issues with AI-verified and human-judgment-needed sections.
Creates well-structured GitHub issues using gh CLI with templates for bugs, features, tasks including titles, descriptions, acceptance criteria, and labels. Use for filing bugs or feature requests.
Generates structured issue reports for GitHub/GitLab repos with code references, media attachments, and session context. Works for bugs, features, and improvements.
Share bugs, ideas, or general feedback.
Turn session insights into a trackable GitHub issue. This skill bridges the gap between "we noticed a problem" and "someone will fix it" — every issue it creates links back to where the idea came from so future readers have full context.
Check the current conversation for a /reflect retrospective or other discussion
about what to improve. If there's a clear reflection with pain points, use that.
If there's no reflection in the conversation, ask the user what they'd like to improve. A single sentence is enough to get started.
If a /reflect produced multiple pain points, ask the user which ones to turn
into issues (they may want one issue, several, or all of them).
Every issue must trace back to its origin so future readers understand the context. Collect these details:
Draft the issue with this structure:
## Problem
What went wrong or what could be better. Be specific — name the files, tools,
or workflows involved.
## Context
Why this matters. What was the user trying to do when this came up.
## Suggested improvement
Concrete next steps. What should change and roughly how.
## Origin
- **Date:** <date>
- **Working directory:** `<path>`
- **Trigger:** <what surfaced this>
Write a concise title (under 70 characters) that captures the improvement, not the session. Good: "Add retry logic to RSS fetcher timeout handling". Bad: "Session reflection issue".
Show the draft title and body. Ask for confirmation before creating. The user might want to adjust scope, wording, or labels.
Use the gh CLI to create the issue in the current repository:
gh issue create --title "<title>" --body "<body>"
Use a HEREDOC for the body to preserve formatting:
gh issue create --title "the title" --body "$(cat <<'EOF'
issue body here
EOF
)"
If the user wants labels, add --label "label1,label2". Common useful labels:
improvement, dx, bug, documentation.
Report the issue URL back to the user when done.