agent-prompts-warmup

Audit and synchronize agent prompt files across coding agent formats.

139|41|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/iamtouchskyer/memex --skill agent-prompts-warmup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-prompts-warmup
Source: https://github.com/iamtouchskyer/memex/tree/main/skills/agent-prompts-warmup
Command: npx skills add https://github.com/iamtouchskyer/memex --skill agent-prompts-warmup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Audit and synchronize agent instruction files across all coding agent formats, ensuring consistency from the first run and beyond.

Core Features & Use Cases

  • Centralizes the source of truth in AGENTS.md and propagates changes to CLAUDE.md, GEMINI.md, and other targets.
  • Detects drift, enforces consistency via pre-commit hooks, and validates with integration tests.
  • Use Case: When cloning a new project, run an audit to verify that all agent prompt files are aligned, then rely on automatic syncing on subsequent edits.

Quick Start

Run the audit to verify scaffolding and drift, then enable automatic syncing to keep prompts aligned.

Frequently Asked Questions about agent-prompts-warmup

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

FAQPage Schema
How do I sync agent prompts across multiple coding platforms?

Detecting agent prompt drift involves auditing instruction files like CLAUDE.md and GEMINI.md against a central AGENTS.md source, enforcing consistency via pre-commit hooks and integration tests.

How do I prevent AGENTS.md drift during ongoing development?

Prevent AGENTS.md drift by applying pre-commit checks and integration tests that validate synchronization, ensuring edits to the central source automatically harmonize across all coding agent formats.

Can I use pre-commit hooks to enforce agent prompt consistency?

Yes, you can enforce agent prompt consistency using pre-commit hooks that validate instruction files against the central AGENTS.md, detecting and preventing drift before changes are committed.

What is the best way to audit coding agent instruction files after cloning a project?

Auditing coding agent instruction files after cloning involves running a script like scripts/postbuild.mjs to verify scaffolding alignment and confirm all agent prompt files match the AGENTS.md source.

Does agent prompt synchronization work with CI-CD pipelines?

Agent prompt synchronization works with CI-CD pipelines by integrating drift detection scripts and tests into the build process, validating that AGENTS.md changes propagate correctly across all targets.

Why do my CLAUDE.md and GEMINI.md files have inconsistent agent instructions?

Inconsistent agent instructions in files like CLAUDE.md and GEMINI.md occur due to drift when updates are applied individually, requiring an audit against a centralized AGENTS.md to restore consistency.