skills.rest
pragsmike
pragsmikeCOMMUNITY
Explore all skills by this author →
GitHub

repo-adaptation

Inspect repositories and produce inventory, classification, and migration reports for agent-facing files.

Updated Apr 3, 2026
Search Tags:#codex#migration#claude#agents#scaffold#opencode#repo-audit
One-click install
npx skills add https://github.com/pragsmike/skills --skill repo-adaptation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-adaptation
Source: https://github.com/pragsmike/skills/tree/main/skills/pragsmike/repo-adaptation
Command: npx skills add https://github.com/pragsmike/skills --skill repo-adaptation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Many repositories either lack a consistent agent-facing surface or use fragmented, tool-specific conventions (CLAUDE.md, .cursorrules, .opencode, etc.), which makes multi-tool workflows error-prone and hard to maintain. This skill helps teams discover what agent instructions exist, classify the repository state, and propose or apply a conservative migration path to a single AGENTS.md plus .agents/ layout.

Core Features & Use Cases

  • Inventory & Inspection: Enumerates agent-facing files and directories with size and a content fingerprint to establish a clear baseline.
  • Classification & Reporting: Classifies repos as greenfield, partial-modern, legacy, or mixed/conflicted and produces a migration report with proposed mappings and compatibility notes.
  • Bootstrap & Conservative Migration: Optionally scaffolds AGENTS.md and the .agents/ tree or migrates legacy files into skills and handoffs while preserving compatibility shims and requiring human approval for destructive actions.
  • Safety-first Rules: Enforces never overwriting AGENTS.md without approval, never deleting legacy files by default, and stopping for human review on conflicts.

Quick Start

Ask the agent to inspect the repository and produce an assessment-mode migration report that inventories agent files and recommends a non-destructive migration plan.

Frequently Asked Questions about repo-adaptation

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

FAQPage Schema
How do I migrate fragmented agent instructions like CLAUDE.md and .cursorrules into a single repository layout?▼

To migrate fragmented agent instructions, this skill inspects repositories containing CLAUDE.md or .cursorrules, inventories existing files, and proposes a conservative migration path to a unified AGENTS.md and .agents/ layout while preserving legacy compatibility shims.

What is the best way to audit a repository for existing AI agent configuration files?▼

Auditing a repository for AI agent configuration files involves enumerating agent-facing files like .opencode or AGENTS.md, calculating content fingerprints, and classifying the repo state as greenfield, partial-modern, legacy, or conflicted to produce a baseline migration report.

Can I assess my repository's agent layout without making any destructive file changes?▼

Yes, you can run an assessment-only inspection that produces a non-destructive migration report, ensuring legacy files are preserved and requiring explicit human approval before any destructive changes or overwrites to AGENTS.md are applied.

How do I scaffold an AGENTS.md file and .agents/ directory tree for a new project?▼

Scaffolding an AGENTS.md file and .agents/ directory tree requires classifying the repository as greenfield, then optionally bootstrapping the standardized layout by migrating legacy instructions into skills and handoffs while maintaining compatibility shims.

What happens when conflicting agent instructions exist across multiple tools in the same repository?▼

When conflicting agent instructions exist across multiple tools, the skill classifies the repository state as mixed or conflicted, stops to flag the conflicts, and requires human review to resolve mappings before proceeding with the migration.

Do I need to manually map tool-specific conventions before standardizing my repository for AI agents?▼

No, manual mapping is unnecessary because the skill automatically produces a migration report with proposed mappings and compatibility notes, translating fragmented tool-specific conventions into a unified AGENTS.md standard.

Related Skills

Explore More Software Engineering Skills→
kaptinlinkaptinlin
23

agent-md-writing

Generate CLAUDE.md and AGENTS.md guidelines from repository structure and docs.

Community
Advanced
JDL440JDL440

Editorial Controls Split Migration

Migrate legacy depth_level to split editorial control fields across UI surfaces.

Community
Advanced
vinnie357vinnie357
12

claude-code-agent-patterns

Apply standardized architectural patterns and tool selections to Claude Code agents.

Community
Advanced
victorp1leonvictorp1leon

repo-audit-safety

Audit Git repositories for governance gaps, safety risks, and non-compliant configurations.

Community
Advanced