Skip to content
Skills Library
Programming · Automation

improve

/improve

Create a structured GitHub issue from a session reflection or improvement idea using the gh CLI. Use this skill when the user asks to create an issue from a reflection, file an improvement, log a lesson learned, or says things like "make an issue for that", "track this", "file that as a bug", "create an improvement issue", or after running /reflect when the user agrees to capture findings. Also use when the user identifies something that should be fixed or improved and wants it tracked in GitHub.

Repository
openpaper ↗
Licence
MIT
Last repository change
08.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create a structured GitHub issue from a session reflection or improvement idea using the gh CLI. Use this skill when the user asks to create an issue from a reflection, file an improvement, log a lesson learned, or says things like "make an issue for that", "track this", "file that as a bug", "create an improvement issue", or after running /reflect when the user agrees to capture findings. Also use when the user identifies something that should be fixed or improved and wants it tracked in GitHub.

Triggers from the description

make an issue for thattrack thisfile that as a bugcreate an improvement issue
Original author description

Create a structured GitHub issue from a session reflection or improvement idea using the gh CLI. Use this skill when the user asks to create an issue from a reflection, file an improvement, log a lesson learned, or says things like "make an issue for that", "track this", "file that as a bug", "create an improvement issue", or after running /reflect when the user agrees to capture findings. Also use when the user identifies something that should be fixed or improved and wants it tracked in GitHub.

How it works

  1. Step 1: Gather the improvement
  2. Step 2: Build the origin reference
  3. Step 3: Structure the issue
  4. Step 4: Confirm with the user
  5. Step 5: Create the issue
Original SKILL.md headings · 83 lines, 394 words
SKILL.md preview
---
name: improve
description: >
  Create a structured GitHub issue from a session reflection or improvement idea
  using the gh CLI. Use this skill when the user asks to create an issue from a
  reflection, file an improvement, log a lesson learned, or says things like
  "make an issue for that", "track this", "file that as a bug", "create an
  improvement issue", or after running /reflect when the user agrees to capture
  findings. Also use when the user identifies something that should be fixed or
  improved and wants it tracked in GitHub.
---

# Improve

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.

## Step 1: Gather the improvement

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).

## Step 2: Build the origin reference

Every issue must trace back to its origin so future readers understand the context.
Collect these details:

1. **Working directory** — the repo/project the session was working in
2. **Date** — today's date
3. **Trigger** — what specifically surfaced this (e.g., "reflection after refactoring the fetcher pipeline" or "user noticed flaky test during PR review")

## Step 3: Structure the issue

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".

## Step 4: Confirm with the user

Show the draft title and body. Ask for confirmation before creating. The user
might want to adjust scope, wording, or labels.

## Step 5: Create the issue

Use the `gh` CLI to create the issue in the current repository:

```bash
gh issue create --title "<title>" --body "<body>"
```

Use a HEREDOC for the body to preserve formatting:

```bash
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.

Versions

RepositoryScoreLicence
This page · falense/openpaper100MIT
terencebristol/terencebristol-toolkit100MIT
spencerbeggs/effected100MIT
crbnos/carbon100AGPL-3.0
zixwei/AI-Fleet-skills100MIT
notque/vexjoy-agent100MIT
motiondivision/motion100MIT
relai-ai/agent-eval-loop100Apache-2.0
jeremylongshore/tons-of-skills-marketplace100MIT

Database snapshot: 13.11.2026 · package version e1c353880b7a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100create-github-issue
    Create GitHub issues using the gh CLI. Use when the user wants to create a new issue, report a bug, request a feature, or create a task in GitHub. Trigger keywords - create issue, new issue, file bug, report bug, feature request, github issue.
  • 100creating-issues
    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking…
  • 100report-issue
    Interactively investigate a bug by grilling the user, exploring the codebase for suspects and solutions, suggesting related test scenarios, and then creating a well-structured GitHub issue via `gh` CLI. Use when the user wants to report a bug, file an issue, create a GitHub…
  • 100create-issue
    This skill should be used when the user asks to "create an issue", "file a bug", "report a problem", "rewrite an issue", or "improve an issue title or body".
  • 100open
    Open a ticket — turn an idea, a bug or an improvement into a GitHub issue, or with `tickets: files` a ticket file under `.10x/`, grounded in the codebase, classified with the repo's own labels or issue types, ready for /10x:work. Use when the user runs /10x:open with something to file.
  • 100create-ticket
    Create or update a GitHub issue for Pulse using the `gh` CLI. Use when the user asks to "file a bug", "create a feature request", "open a GitHub issue", or "update an existing one". Supports feature, bug, and refactor issue types with structured templates; shows a draft for…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.