New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Renumber Adr

by fullsend-ai in fullsend-ai/fullsend

Check whether ADR numbers in the current branch conflict with ADRs already on the PR's target branch, and renumber if needed.

Apache-2.0Auto-check passedDevelopment

Install Renumber Adr

skills CLI
$ npx skills add fullsend-ai/fullsend --skill renumber-adr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fullsend-ai/fullsend renumber-adr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fullsend-ai/fullsend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/renumber-adr .claude/skills/renumber-adr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
renumber-adr
GitHub stars
149
Token cost
~1.4k tokens
SKILL.md length
728 words
Files
2 (incl. scripts)
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Check whether ADR numbers in the current branch conflict with ADRs already on the PR's target branch, and renumber if needed.

  • Works in 7 steps: Identify new ADR files in this branch → Check for number collisions → Collect in-flight ADR numbers and check… → …
  • Tasks that involve Architecture decision records
  • SKILL.md covers Overview, When to Use, Process and Constraints
  • Runs Shell scripts from its folder; calls git, gh and bash

What it does

Renumber Adr is an agent skill from fullsend-ai/fullsend. Check whether ADR numbers in the current branch conflict with ADRs already on the PR's target branch, and renumber if needed. Use before merging a PR that adds new ADRs, to avoid number collisions with concurrently merged ADRs.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/inflight-adr-numbers.sh`).

It sits in Development, covering Architecture decision records. The repository describes itself as: On the path to fully autonomous agentic engineering. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Architecture decision records

Example prompts

  • “/renumber-adr”

Requirements

  • A Bash shell

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Identify new ADR files in this branch
  2. Check for number collisions
  3. Collect in-flight ADR numbers and check for collisions
  4. Rename the file
  5. Update references inside the ADR
  6. Update references across the repository
  7. Verify and report

What it can do on your machine

Read from SKILL.md and the folder at commit 6c6be1e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • gh
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Renumber Adr loads about 1.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 728 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from fullsend-ai/fullsend at commit 6c6be1e, republished under its Apache-2.0 licence (© fullsend-ai). 728 words, ~1,391 tokens.

Download SKILL.mdSave it as .claude/skills/renumber-adr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
renumber-adr
description
Check whether ADR numbers in the current branch conflict with ADRs already on the PR's target branch, and renumber if needed. Use before merging a PR that adds new ADRs, to avoid number collisions with concurrently merged ADRs.

Renumber ADR

Overview

When multiple PRs add ADRs concurrently, they may pick the same four-digit number. This skill detects collisions against the target branch and against ADR numbers introduced by other open PRs, then renumbers the ADR file, its internal title/heading, and every reference to it across the repository.

When to Use

  • Before merging a PR that introduces one or more new ADR files.
  • When the user asks to check or fix ADR numbering.
  • When invoked via /renumber-adr.

Process

Follow these steps in order. Do not skip steps.

1. Identify new ADR files in this branch

Determine the target branch for the PR. If the user provides it as an argument, use that. Otherwise:

bash
gh pr view --json baseRefName --jq '.baseRefName' 2>/dev/null || echo main

Then find ADR files that are new in this branch (not present on the target):

bash
git diff --name-only --diff-filter=A <target-branch>...HEAD -- docs/ADRs/

If no new ADR files are found, report that there is nothing to renumber and stop.

2. Check for number collisions

List existing ADR files on the target branch:

bash
git ls-tree --name-only <target-branch> docs/ADRs/

For each new ADR file, extract its four-digit number from the filename (NNNN-short-description.md). Check whether any file with the same NNNN prefix exists on the target branch.

If there are no collisions with the target branch, continue to step 3 anyway — there may still be collisions with numbers claimed by other open PRs.

3. Collect in-flight ADR numbers and check for collisions

Collect all taken ADR numbers from these three sources:

  1. Target branch ADR files (from step 2).
  2. Other new ADR files in this branch (to avoid collisions among the branch's own ADRs).
  3. ADR files introduced by other open PRs. This is critical — multiple PRs may be adding ADRs concurrently. Run the helper script to collect every ADR number from open PRs targeting the same base branch:
bash
bash skills/renumber-adr/scripts/inflight-adr-numbers.sh <target-branch> <current-pr-number>

Pass the current PR number so the script excludes it (avoiding self-collision). The script prints one four-digit number per line. If it produces no output, there are no in-flight ADR numbers to worry about.

Combine all three sets of taken numbers. For each new ADR in this branch, check whether its number appears in the combined set. If none of the new ADR numbers collide with any taken number, report that all numbers are clear and stop.

For each colliding ADR, pick the lowest unused four-digit number.

4. Rename the file
bash
git mv docs/ADRs/NNNN-old-slug.md docs/ADRs/MMMM-old-slug.md
5. Update references inside the ADR

The ADR file itself contains the number in several places. Update all of them:

  • Frontmatter title: e.g. title: "2. Initial Fullsend Design" — uses the number without leading zeros.
  • Markdown heading: e.g. # 2. Initial Fullsend Design — same format.

Read the file and update these occurrences. The number in the title and heading uses the integer form (no leading zeros), not the four-digit padded form.

Show full SKILL.md (280 more words)Show less
6. Update references across the repository

Search the entire repository for references to the old ADR and update them. There are several patterns to find:

  1. Filename references (in markdown links): NNNN-slug.md — update the four-digit prefix to the new number.
  2. Display text references: ADR NNNN — update the four-digit number in link text and plain text.
  3. Section heading references in prose (e.g. ## Reference workflow components (ADR NNNN)) — update the number.

Search broadly:

bash
# Find all files referencing the old filename
grep -rl "NNNN-slug" .

# Find all files referencing "ADR NNNN" (display text or plain text)
grep -rl "ADR NNNN" .

For each file found, read it and update all occurrences. Be careful to match the exact old filename and number — do not accidentally rename unrelated four-digit sequences.

7. Verify and report

After all renames and reference updates:

  • List the changes made: old filename -> new filename, and the count of files with updated references.
  • Run pre-commit run --files <all-changed-files> to verify nothing is broken.
  • Report the result to the user.

Constraints

  • Only renumber ADRs that are new in this branch. Never renumber ADRs that already exist on the target branch.
  • Preserve the slug. Only the four-digit number prefix changes; the descriptive slug (short-description) stays the same.
  • Update every reference. A missed reference is a broken link. Search thoroughly.
  • Handle multiple ADRs. If the branch adds several ADRs and more than one collides, renumber all of them before updating references (so cross-references among the new ADRs are correct).
  • Check open PRs. Always check ADR numbers introduced by other open PRs targeting the same base branch. A number that is clear on the target branch today may collide with another PR that merges first.
  • Do not modify ADR content beyond the number in the title and heading. Substantial ADR content is not rewritten once accepted; this skill only fixes numbering.

© fullsend-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in skills/renumber-adr of fullsend-ai/fullsend.

  • SKILL.md
  • scripts/inflight-adr-numbers.sh

Open the folder on GitHubat commit 6c6be1e

Compare with similar skills

Renumber Adr next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Renumber Adr compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Renumber Adr this skillfullsend-ai/fullsend149—~1.4kAutomated safety check: PassApache-2.0
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Architecture DecisionDonchitos/Claude-Code-Game-Studios26k—~1.7kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0
Domain Modelingbrim-borium/spotify_sdk1665 repos~806Automated safety check: PassApache-2.0

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed

  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed

  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 5 repos~806 tokens
    DevelopmentAuto-check passed

  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    176 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed

More from fullsend-ai/fullsend

All 15 skills in this repo

  • Cutting Releases

    fullsend-ai/fullsend

    A skill your agent uses when the user wants to tag a release, cut a release candidate, or ship a new version.

    149 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Topissues

    fullsend-ai/fullsend

    Build a merged RICE priority table: top unassigned backlog issues plus issues assigned to the current user.

    149 GitHub stars~523 tokensUpdated today
    Auto-check passed

  • User Forum Whats New

    fullsend-ai/fullsend

    A skill your agent uses when preparing the Fullsend user forum "What's New" agenda, a Tuesday-to-Tuesday recap, forum-host talk-track notes, or copy-paste HTML of shipped changes for users.

    149 GitHub stars~4k tokensUpdated today
    Auto-check passed

  • Adr Corner

    fullsend-ai/fullsend

    Find open GitHub pull requests that add or change Architecture Decision Records and report attribution, summaries, discussion points, and dates.

    149 GitHub stars~654 tokensUpdated today
    Auto-check passed

  • Nextwork

    fullsend-ai/fullsend

    Build a readiness-oriented queue of open issues/PRs — assigned work plus their open GitHub blockers — and recommend the next action for each.

    149 GitHub stars~5.3k tokensUpdated today
    Auto-check passed

  • Analyze Transcript

    fullsend-ai/fullsend

    Analyze fullsend agent run transcripts from GitHub Actions artifacts.

    149 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Renumber Adr

What does Renumber Adr do?

Check whether ADR numbers in the current branch conflict with ADRs already on the PR's target branch, and renumber if needed. Renumber Adr is an agent skill from fullsend-ai/fullsend. Check whether ADR numbers in the current branch conflict with ADRs already on the PR's target branch, and renumber if needed.

When should I use Renumber Adr?

Renumber Adr fits situations like: tasks that involve Architecture decision records.

How do I install Renumber Adr in Claude Code?

Run `npx skills add fullsend-ai/fullsend --skill renumber-adr -a claude-code`. Or copy the skill folder (skills/renumber-adr in fullsend-ai/fullsend) into .claude/skills/renumber-adr in your project. Claude Code loads it when a task matches its description.

How do I install Renumber Adr in Codex?

Run `npx skills add fullsend-ai/fullsend --skill renumber-adr -a codex`. Or copy the skill folder (skills/renumber-adr in fullsend-ai/fullsend) into .agents/skills/renumber-adr in your project. Codex loads it when a task matches its description.

Can I use Renumber Adr in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fullsend-ai/fullsend --skill renumber-adr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/renumber-adr, .gemini/skills/renumber-adr, .github/skills/renumber-adr and .opencode/skills/renumber-adr in your project.

What does Renumber Adr need to run?

Going by SKILL.md and its folder, Renumber Adr needs a shell for the scripts in its folder and the command-line tools its instructions call (git, gh and bash). Our summary lists: A Bash shell.

Does Renumber Adr access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Renumber Adr safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Renumber Adr use?

Renumber Adr is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Renumber Adr use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Renumber Adr?

Skills that share tags, products or a category with Renumber Adr: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars) and Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Renumber Adr?

fullsend-ai (a GitHub organization) maintains it in fullsend-ai/fullsend, which has 149 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.

Source: fullsend-ai/fullsend on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.