renumber-adr

Detect ADR numbering conflicts and renumber files before merging PRs.

107|81|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/fullsend-ai/fullsend --skill renumber-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: renumber-adr
Source: https://github.com/fullsend-ai/fullsend/tree/main/skills/renumber-adr
Command: npx skills add https://github.com/fullsend-ai/fullsend --skill renumber-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Detect ADR numbering collisions against the target branch and renumber the ADR file, its internal title/heading, and every reference to it across the repository.
  • Prevents numbering collisions when multiple PRs add ADRs concurrently.
  • Use before merging PRs to ensure unique ADR numbers and maintain repository consistency.

Quick Start

Run the renumber-adr process on your feature branch before merging to ensure ADR numbers do not collide.

Frequently Asked Questions about renumber-adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent ADR number collisions when merging multiple pull requests?

To prevent ADR number collisions when merging multiple pull requests, run an auto-renumbering process on your feature branch to detect conflicts against the target branch and renumber files before merging.

What happens to cross-references when renumbering ADR files in a git repository?

When renumbering ADR files in a git repository, the process updates cross-references across the repository, renames the ADR files, and modifies their internal titles and headings without altering content beyond the numbering.

When do I need to renumber ADRs before merging a branch?

You need to renumber ADRs before merging a branch when the PR introduces new ADRs that might conflict with ADRs already on the target branch, especially if multiple PRs adding ADRs are merged concurrently.

Does the ADR renumbering process change the content of my architecture decision records?

No, the ADR renumbering process does not change the content of your architecture decision records. It only renames files, updates titles and headings, and updates cross-references without altering content beyond the numbering.

How do I resolve ADR numbering conflicts between a feature branch and the target branch?

To resolve ADR numbering conflicts between a feature branch and the target branch, run a renumbering process that detects collisions across the target branch and branch-local new ADRs, then automatically renumbers the conflicting files.

What's the best way to manage ADR numbering across concurrent pull requests?

The best way to manage ADR numbering across concurrent pull requests is to run an auto-renumbering process on each feature branch before merging, which detects collisions against the target branch and renumbers ADRs to ensure unique numbers.