core-rule-maintenance

Synchronize CLAUDE.md and AGENTS.md core rules across three environments.

10|7|Updated Sep 24, 2025

Search Tags:#automation #workflow #synchronization #maintenance #CLAUDE.md #AGENTS.md

Ready to run

npx skills add https://github.com/matsuni-kk/agent_template_public --skill core-rule-maintenance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: core-rule-maintenance
Source: https://github.com/matsuni-kk/agent_template_public/tree/main/.cursor/skills/core-rule-maintenance
Command: npx skills add https://github.com/matsuni-kk/agent_template_public --skill core-rule-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains core rules across CLAUDE.md and AGENTS.md with cross-environment synchronization.

Core Features & Use Cases

Interactive preflight review of CLAUDE.md/AGENTS.md to assess changes and impact.
Change orchestration for CLAUDE.md updates, core-rule changes, new rule additions, and path dictionary/workflow index updates.
Three-environment synchronization to ensure consistency across master, staging, and production-like contexts.
Automatic alignment of Next Action triggers and workflow indices after updates.

Quick Start

Instruct the system to update CLAUDE.md and AGENTS.md and propagate the changes across all environments.

Frequently Asked Questions about core-rule-maintenance

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

FAQPage Schema

How do I keep CLAUDE.md and AGENTS.md core rules synchronized across multiple environments?▼

To synchronize core rules across CLAUDE.md and AGENTS.md, you can apply a three-environment maintenance workflow that propagates updates from master to staging and production contexts. This ensures consistency through preflight reviews and controlled change orchestration.

What is the best way to safely apply new rules to CLAUDE.md without breaking existing agent workflows?▼

The safest way to apply new rules to CLAUDE.md is to use a preflight review process that assesses impact before changes are committed. This approach enforces controlled change propagation and automatically aligns Next Action triggers and workflow indices after the update.

How does cross-environment synchronization work for CLAUDE.md path dictionary updates?▼

Cross-environment synchronization works by orchestrating path dictionary updates across three distinct environments, ensuring that master, staging, and production-like contexts remain consistent. It refreshes workflow indices and aligns triggers to maintain auditable updates.

Can I use an automated workflow to update both core rules and workflow indices simultaneously?▼

Yes, you can automate the update of core rules and workflow indices simultaneously. The maintenance workflow handles CLAUDE.md updates, core-rule changes, and path-dictionary refreshes together, enforcing preflight reviews and automatic alignment of Next Action triggers for safe, auditable results.

Do I need a preflight review before updating AGENTS.md in a production-like environment?▼

Yes, a preflight review is required before updating AGENTS.md in any environment. This step assesses potential changes and their impact, ensuring controlled change propagation and preventing unsanctioned modifications from reaching staging or production-like contexts.

Why does my core rule change not reflect in the Next Action triggers across all environments?▼

Core rule changes may not reflect in Next Action triggers if cross-environment synchronization is incomplete. You must enforce automatic alignment of triggers and workflow indices after updates, ensuring the three-environment maintenance workflow propagates all changes consistently.