What is backfill-issues?

A workflow for creating issue-tracker tasks from merged GitHub pull requests that do not already have matching issues.

It helps inspect merged pull requests, find untracked work, group related changes, and prepare proposed issues for human approval.

It captures completed work that might otherwise be missing from the current sprint's tracking, while grouping related pull requests and requiring review before creation.

How AlexisBalayre/claude-code-power-config configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AlexisBalayre/claude-code-power-config/main/.claude/skills/backfill-issues/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-config

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/backfill-issues/github.svg)](https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/backfill-issues)

Your own site

<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/backfill-issues"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/backfill-issues/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/backfill-issues"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/backfill-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 943 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00023	$0.00943
Opus 5.5	$0.00009	$0.00377
Sonnet 5.5	$0.00005	$0.00189
Haiku 4.5	$0.00002	$0.00094

Measured 2mo ago against content hash 6f7bc380a403, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

backfill-issues scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/backfill-issues/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Issue Generator from Merged PRs

You generate tracker issues from merged GitHub PRs that lack corresponding issues. You group related PRs into single issues and require user review before creation.

Setup: this skill files through an issue-tracker MCP server (examples use a Linear-style API). Fill in your own IDs via .env (see .env.example) and enable the server in .claude/settings.local.json. The mcp__linear-server__* tool names are placeholders — swap them for your tracker's tools.

Tracker Metadata

Read these from .env (never hardcode real account IDs in the repo):

Assignee: ${TRACKER_ASSIGNEE_ID}
Team: ${TRACKER_TEAM_ID}
Project: ${TRACKER_PROJECT_ID}

Workflow

1. Date Range & Context

Check $ARGUMENTS for --since YYYY-MM-DD.
If missing, call mcp__linear-server__list_cycles(teamId: "${TRACKER_TEAM_ID}", type: "current").
Use the cycle's startDate. Inform the user of the start date being used.

2. Fetch Merged PRs

Execute:

gh pr list --author=@me --state=merged --search="merged:>=YYYY-MM-DD" --json number,title,url,mergedAt,body --limit 100

Stop if no PRs are found.

3. Filter Linked PRs

Call mcp__linear-server__list_issues(assignee: "${TRACKER_ASSIGNEE_ID}", team: "${TRACKER_TEAM_ID}").

Exclude PRs where the URL exists in an issue description or attachment.
Exclude PRs where the body contains "Closes ${TRACKER_ISSUE_PREFIX}-XXXX" (flag these to the user).
Report the count of filtered/skipped PRs. Stop if none remain.

4. Auto-Group Logic

Group unlinked PRs based on:

Scope/Prefix: (e.g., fix(engine):, feat(api):).
Semantic Similarity: Related features or bug fixes.
Labels:
- feat: → Feature
- fix: → Bug
- chore:/refactor: → Chore
- perf: → Improvement
Estimates: 1 PR = 1pt, 2-3 PRs = 2pts, 4+ PRs = 3pts.

5. Present Proposal

Display the groups clearly:

📋 Proposed Issues (X groups from Y PRs)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Group 1: "title" [Label] (N pts)
  - #PR_NUM title
...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Skipped: Z PRs

Read the full file on GitHub · 108 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 108 lines · 23 tokens per session scan A 6f7bc380a403

Subscribe to this mod's changes

backfill-issues is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 943 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Project management agents ai anthropic claude developer-tools

claude-code-power-config: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Issue Generator from Merged PRs

Tracker Metadata

Workflow

1. Date Range & Context

2. Fetch Merged PRs

3. Filter Linked PRs

4. Auto-Group Logic

5. Present Proposal

What this file has done since we first saw it

Other skills, from other repositories

operator-scorecard

github-monitor

heartbeat

shiplog

idea-pipeline

strategy-builder