artgraph-rename

Rename, split, and merge requirement IDs across specs, code, and tests.

12|2|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/mori-shin-x/artgraph --skill artgraph-rename
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: artgraph-rename
Source: https://github.com/mori-shin-x/artgraph/tree/main/.cursor/skills/artgraph-rename
Command: npx skills add https://github.com/mori-shin-x/artgraph --skill artgraph-rename

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the challenge of maintaining consistency when requirement IDs change, preventing drift between your specifications, implementation code, and test suites.

Core Features & Use Cases

  • Atomic Refactoring: Safely rename, split, or merge requirement IDs across specs, @impl tags, and test files.
  • Integrity Verification: Automatically updates .trace.lock files and ensures that requirement coverage remains intact during restructuring.
  • Use Case: When a complex requirement needs to be broken down into smaller, more manageable tasks, this skill handles the tedious process of updating all references and tags across the entire codebase.

Quick Start

Use the artgraph-rename skill to split the requirement REQ-001 into REQ-101 and REQ-102 after verifying the working tree is clean.

Frequently Asked Questions about artgraph-rename

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

FAQPage Schema
How do I safely rename requirement IDs across specs, source code, and tests?

Split or merge requirement IDs by applying atomic refactoring operations that update all references across specifications, @impl tags, and test files simultaneously to prevent traceability drift.

How do I split or merge requirement IDs without breaking traceability?

Split or merge requirement IDs by applying atomic refactoring operations that update all references across specifications, @impl tags, and test files simultaneously to prevent traceability drift.

How does requirement drift detection work when refactoring IDs?

Requirement drift detection works by validating changes through dry-runs and automatically updating .trace.lock files to ensure deterministic traceability and system consistency remain intact during restructuring.

Can I use this refactoring tool without an LLM modifying my codebase?

Yes, you can use this refactoring tool without an LLM, as it operates deterministically to validate changes and update lock files, ensuring system consistency without requiring LLM intervention.

What do I need to do before splitting a requirement ID like REQ-001?

Before splitting a requirement ID, you need to verify that your working tree is clean to ensure the atomic refactoring operation can safely apply changes and update the lock file.