regenerate-skill

Regenerate generated skills while preserving the User Customizations zone verbatim.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill regenerate-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regenerate-skill
Source: https://github.com/chaletteholdings/command-room-releases-2710/tree/main/command-room/skills/regenerate-skill
Command: npx skills add https://github.com/chaletteholdings/command-room-releases-2710 --skill regenerate-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerates an existing generated skill when the template or project context changes, while preserving the User Customizations zone verbatim and flagging non-zone edits for merge review. Reads the current SKILL.md and its shadow file (.generated/SKILL.md.current), diffs them to detect non-zone edits, then re-runs skill-generator with a preview-before-commit gate, 30-day rollback history, and explicit merge prompts for any content the user changed outside the customization markers.

Core Features & Use Cases

  • Detects non-zone edits by comparing the current SKILL.md to its shadow, preserving user customizations.
  • Applies template/context updates with a 30-day rollback window and provenance tracking.
  • Provides a preview-before-commit regeneration flow with explicit merge prompts for non-zone edits and an audit trail of regenerations.
  • Supports targeted regeneration commands such as "regenerate [project] skill", "update the [project] skill", and drift-detection via weekly-audit.

Quick Start

Say "regenerate [project] skill" to refresh the generated skill while preserving customizations.

Frequently Asked Questions about regenerate-skill

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

FAQPage Schema
How do I regenerate a skill while preserving user customizations?▼

To regenerate a skill while preserving customizations, the tool reads the current SKILL.md and its shadow file, diffs them to detect non-zone edits, and re-runs the skill-generator with a preview-before-commit gate while keeping the User Customizations zone verbatim.

How does skill drift detection work when templates or project context changes?▼

Skill drift detection works by comparing the current SKILL.md against its shadow file in the .generated directory to flag non-zone edits, which can be triggered by a weekly-audit or by requesting an update to the project skill.

Can I rollback a skill regeneration if the new version breaks my workflow?▼

Yes, you can rollback a skill regeneration because the tool maintains a 30-day rollback history with history snapshots written to the workspace, allowing you to revert to a previous skill version if needed.

What happens to manual edits made outside the customization markers during a skill update?▼

When a skill update detects manual edits outside the customization markers, it triggers explicit merge prompts for merge review, ensuring non-zone edits are flagged and handled before the new skill version is committed.

When should I use a skill regeneration workflow instead of manual edits?▼

You should use a skill regeneration workflow when a template or project context changes and you need to safely apply updates across generated skills, utilizing the preview-before-commit gate and provenance tracking to prevent losing custom configurations.