skills.rest
NSEvteev
NSEvteevCOMMUNITY
Explore all skills by this author →
GitHub

rule-modify

Modify Claude Code rule definitions and statuses within .claude/rules directory.

31|5|Updated Jan 14, 2026
Search Tags:#migration#rename#claude-code#deactivation#rules-management#rule-modification
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill rule-modify-nsevteev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rule-modify
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/rule-modify
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill rule-modify-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the lifecycle management of Claude Code rules by updating, deactivating, or migrating rule files stored under .claude/rules/. It ensures changes are traceable and consistently applied across environments.

Core Features & Use Cases

  • Update rule content in the .claude/rules directory to reflect new requirements or corrections.
  • Deactivate outdated rules to prevent their use while preserving historical context.
  • Migrate rules to new file paths or formats to support evolving architectures and SSOT guidelines.
  • Rename rules with proper versioning to maintain clear provenance and avoid conflicts.

Quick Start

Invoke the command /rule-modify with the rule name to apply an update, deactivation, or migration following the SSOT guidelines.

Frequently Asked Questions about rule-modify

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

FAQPage Schema
How do I safely modify Claude Code rules stored in .claude/rules?▼

To modify Claude Code rules safely, update the rule definitions within the .claude/rules directory while conforming to SSOT templates. This ensures changes are traceable and consistently applied across environments without conflicts.

What is the best way to deactivate outdated rules without losing historical context?▼

Deactivating outdated rules involves updating their status within .claude/rules to prevent their use while preserving the original files. This approach phases out deprecated rules safely and maintains clear historical documentation.

How do I migrate rules to new file paths in Claude Code?▼

Migrating rules to new file paths requires applying scope to rename or move the rule files under .claude/rules. Proper versioning maintains clear provenance and avoids conflicts during the migration process.

Do I need SSOT templates to manage rule modifications in Claude Code?▼

Yes, conforming to SSOT templates and following the modify-rule SSOT instructions is required to avoid conflicts and maintain traceability. This ensures all rule updates, deactivations, and migrations are consistently applied.

Why does renaming rules require proper versioning in .claude/rules?▼

Renaming rules requires proper versioning to maintain clear provenance and avoid conflicts within the .claude/rules directory. This practice ensures that migrated or updated rules remain traceable across evolving architectures.

Related Skills

Explore More Software Engineering Skills→
ReScienceLabReScienceLab
10

using-git-worktrees

Create an isolated git worktree for a feature branch with automatic project setup.

Official
Advanced
TMI-appsTMI-apps
2

improve-rule

Rewrites rules to meet defined quality standards with structured markdown output.

Official
Intermediate
EigenwiseEigenwise
15

manage-rules

Inspect, audit, and toggle project live-rules for Claude Code workspaces.

Community
Advanced
oogDZoogDZ

rule-create

Create rule files with frontmatter and register them in the Claude rules registry.

Community
Intermediate