backfill-issues SKILL.md skillB

backfill-issues from alexisbalayre/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add alexisbalayre/claude-code-config/backfill-issues@git:20260711.4f85074

Pins git:20260711.4f85074 in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
alexisbalayre/claude-code-config
Path
.claude/skills/backfill-issues/SKILL.md
Versions recorded
1
Latest version
git:20260711.4f85074, committed Jul 11, 2026
Size
3,635 bytes
Repository stars
3
License
MIT

Generate tracker issues from merged PRs for the current sprint following strict grouping and review rules.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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:

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

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gdyf4qdbxdmbokfh/6f7bc380a403d0eff4770c4d657a29deaf941efec5fac8c2c65846613ead1e0d.json

Then /plugin install backfill-issues@markdownregistry-gdyf4qdbxdmbokfh in Claude Code. It installs git:20260711.4f85074, the one graded B here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add alexisbalayre/claude-code-config/backfill-issues@sha256:6f7bc380a403d0ef

The line at the top of this page pins the label git:20260711.4f85074, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_gdyf4qdbxdmbokfh.svg)](https://markdownregistry.com/a/art_gdyf4qdbxdmbokfh)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in alexisbalayre/claude-code-config/backfill-issues since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of backfill-issues from somewhere else? Ask it: where did my backfill-issues come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Jul 11, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260711.4f85074 latest2026-07-11 4f85074 3,635 BB view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: No instruction to read or print local credentials (matched: Read these from `.env)
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (3635 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

alexisbalayre/claude-code-config · 3 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_gdyf4qdbxdmbokfh
GET https://markdownregistry.com/api/v1/resolve?ref=alexisbalayre/claude-code-config/backfill-issues
GET https://markdownregistry.com/api/v1/blob/6f7bc380a403d0eff4770c4d657a29deaf941efec5fac8c2c65846613ead1e0d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from alexisbalayre/claude-code-config

README Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/README.md
git:20261017.c5ad833 · audit A · 3 stars
architecture-explainer Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/architecture-explainer.md · Use PROACTIVELY when the user asks why or how about the system architecture — component boundaries, data flow, request…
git:20260917.a589e3f · audit A · 3 stars
comment-pruner Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/comment-pruner.md · Autonomously prune bad comments from code added in the current session. Dispatched by the comment-pruner Stop hook when…
git:20260917.a589e3f · audit A · 3 stars
convention-checker Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/convention-checker.md · Use PROACTIVELY to verify files follow area-specific coding standards before committing. MUST BE USED after editing…
git:20260917.a589e3f · audit A · 3 stars
migration-reviewer Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/migration-reviewer.md · Use PROACTIVELY after any change to database schema definitions (ORM models, schema files) or to migration files (new…
git:20260917.a589e3f · audit A · 3 stars
review-context Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-context.md · Reviews changed code for spec contradictions, protocol violations, and infrastructure anti-patterns. Spawned by the…
git:20260811.6af4418 · audit A · 3 stars
review-conventions Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-conventions.md · Audits changed files for compliance with the project's documented rules and accepted ADR decisions. Spawned by the…
git:20260917.a589e3f · audit A · 3 stars
review-correctness Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-correctness.md · Reviews changed code for logic and behavior defects that deterministic tooling cannot catch, including behavioral…
git:20261017.279b6aa · audit A · 3 stars
review-docs Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-docs.md · Reviews the quality, accuracy, and usefulness of prose a change introduces. Strict on low-value comments and…
git:20260917.a589e3f · audit A · 3 stars
review-maintainability Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-maintainability.md · Reviews changed code for structural regressions that make the codebase harder to maintain. Spawned by the pr-ci-review…
git:20261017.c5ad833 · audit A · 3 stars
review-security Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-security.md · Reviews changed code for real, reachable security issues at system boundaries. Spawned by the pr-ci-review skill.
git:20261017.279b6aa · audit A · 3 stars
review-spec Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-spec.md · Checks a change against the issue or spec it implements, for requirements missing, partial, or built wrong, and for…
git:20261017.c5ad833 · audit A · 3 stars

Every file in alexisbalayre/claude-code-config

Browse by kind, by grade B, or by owner.