prompts-rewrite-all

Rewrite prompt-oriented markdown files into Claude Code guidance with diff-first approval.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill prompts-rewrite-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prompts-rewrite-all
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/prompts-rewrite-all
Command: npx skills add https://github.com/hirokimry/vibecorp --skill prompts-rewrite-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams safely refactor prompt-heavy markdown so instructions stay clear, aligned, and consistent across a repository.

Core Features & Use Cases

  • Review and rewrite skill files, agent docs, and rule files.
  • Check rewritten prompts against Claude Code guidance before changing behavior.
  • Keep distribution copies synchronized after approved edits. Use case: When a repository's prompt instructions drift, use this Skill to propose a controlled rewrite instead of editing files blindly.

Quick Start

Ask the skill to review the prompt files in your repository and propose approved rewrites for any instructions that no longer follow the current standard.

Frequently Asked Questions about prompts-rewrite-all

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

FAQPage Schema
How do I safely refactor prompt markdown files in a repository without breaking agent instructions?

Rewriting agent instructions requires checking revised prompts against official Claude Code guidance before changing behavior. This validation step ensures refactored markdown files remain aligned with current specifications and do not introduce conflicting commands.

What is the best way to keep distribution copies of rule documents synchronized after a prompt rewrite?

Synchronizing distribution copies involves pushing approved prompt edits to all repository mirrors without auto-merging. This ensures markdown rule documents stay consistent and prevents silent specification drift across different agent instruction files.

How do I review markdown prompt files against Claude Code docs before committing changes?

Reviewing prompt files against Claude Code docs requires a validation step that compares proposed markdown rewrites with official guidance. This specification alignment check happens before the diff approval flow to prevent breaking existing agent behavior.

Can I use a diff-first approval flow for bulk prompt refactoring across multiple skill files?

Bulk prompt refactoring across skill files supports a diff-first approval flow to review all proposed markdown changes before execution. This allows teams to manage multiple agent instruction rewrites simultaneously while maintaining strict specification alignment.

Why does rewriting agent instructions require checking official Claude Code documentation first?

Checking official Claude Code documentation before rewriting agent instructions ensures refactored markdown prompts align with current behavioral specifications. This prevents agent instruction drift and maintains safe, consistent guidance across the repository.

When should I avoid auto-merging markdown rule documents during prompt refactoring?

Avoid auto-merging markdown rule documents when agent instructions require precise specification alignment during refactoring. A manual diff-first approval flow prevents silent behavioral changes that auto-merge would otherwise introduce to distribution copies.