n-adr-normalize

Normalize Architecture Decision Record drafts via LLM batch processing in isolated git-worktrees.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/vitaliytv/7n --skill n-adr-normalize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n-adr-normalize
Source: https://github.com/vitaliytv/7n/tree/main/.cursor/skills/n-adr-normalize
Command: npx skills add https://github.com/vitaliytv/7n --skill n-adr-normalize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @nitra/cursor.

What problem does it solve?

This skill automates the tedious process of normalizing Architecture Decision Record (ADR) drafts, ensuring that documentation remains consistent and clean without requiring manual intervention for every batch.

Core Features & Use Cases

  • Automated Normalization: Runs LLM-based processing on ADR drafts to enforce structure and formatting.
  • Flexible Execution: Supports dry-runs to preview changes and batch processing to handle large volumes of drafts efficiently.
  • Use Case: When you have a backlog of ADR drafts that need to be formatted and merged into the main documentation, this skill processes them in batches, allowing you to review and commit the changes with minimal effort.

Quick Start

Run the n-adr-normalize skill to process the current batch of ADR drafts and prepare them for review.

Frequently Asked Questions about n-adr-normalize

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

FAQPage Schema
How do I normalize Architecture Decision Record drafts automatically?

You can normalize Architecture Decision Record (ADR) drafts using LLM-driven batch processing to enforce structural consistency. The Skill operates within isolated git-worktrees to manage documentation updates safely without interfering with main development branches.

What is the best way to batch process ADR formatting without breaking my main git branch?

Batch processing ADR formatting safely is achieved by executing LLM-based normalization within isolated git-worktrees. This prevents interference with your main development branches while performing automated file rewrites and cleanup tasks across large volumes of drafts.

Do I need a specific toolchain to automate ADR cleanup?

Automating ADR cleanup requires the @nitra/cursor toolchain and a configured environment. These dependencies are necessary for the Skill to execute automated file rewrites and perform LLM-driven structural normalization.

Can I preview ADR normalization changes before committing them?

You can preview ADR normalization changes before committing by using the Skill's dry-run execution mode. Dry-runs allow you to review formatting adjustments and structural modifications before merging processed drafts into your main documentation.

When do I need to normalize ADR drafts with an LLM?

You need to normalize ADR drafts with an LLM when you have a backlog of documentation that requires structural consistency. This approach ensures formatting remains clean across large volumes of drafts without requiring manual intervention for every batch.

What are the limitations of using git-worktrees for ADR documentation updates?

Using git-worktrees for ADR documentation updates limits processing to isolated branch environments to prevent main branch interference. Consequently, the Skill requires a properly configured environment and the @nitra/cursor toolchain to execute automated file rewrites successfully.