johnpapa/ai-ready

Agent Skill that analyzes your repo and generates the AI-ready configuration coding agents need — AGENTS.md, copilot-instructions, CI, issue templates, and more. Works in Claude Code, GitHub Copilot, Codex, and Cursor.

201

stars

147

commits

Sep 9, 2026

updated

agents
agent-skills
agents-md
ai-ready
claude-code
codex
copilot
copilot-cli
copilot-plugin
cursor
developer-experience
skills

README

AI Ready

AI Ready Version

An Agent Skill that analyzes your repository and generates the configuration files AI agents need to contribute correctly. GitHub-native — it auto-discovers your repo's context, community health, and PR review patterns without you explaining anything.

Works in GitHub Copilot, Claude Code, OpenAI Codex, Cursor, and any other tool that supports the Agent Skills standard.

Quick Start

Any agent, one command

The open skills CLI installs into Claude Code, Codex, Cursor, Copilot, and 70+ other agents:

npx skills add johnpapa/ai-ready

That's it — no per-tool setup. Restart your agent afterward.

Native plugin installs

Prefer your tool's own plugin system? Each of these installs the same skill.

ToolInstall
GitHub Copilot CLIcopilot plugin install ai-ready@awesome-copilot
Claude Code/plugin marketplace add johnpapa/ai-ready
/plugin install ai-ready@johnpapa-ai-ready
OpenAI Codexcodex plugin marketplace add johnpapa/ai-ready
codex plugin add ai-ready@johnpapa-ai-ready
CursorCopy skills/ai-ready/ into ~/.cursor/skills/ai-ready/
Anything elseCopy skills/ai-ready/ into ~/.agents/skills/ai-ready/

Claude and Codex each need two commands — the first registers the marketplace, the second installs the plugin from it.

Copilot CLI installs from the built-in awesome-copilot marketplace. Installing straight from a repo (copilot plugin install johnpapa/ai-ready) still works but is deprecated, so prefer the marketplace form.

~/.agents/skills/ is the vendor-neutral Agent Skills directory that Codex and Cursor both read, so the last row works for most tools.

If a marketplace mirrors this skill, it should point to a release tag such as v1.3.0, not a raw commit SHA.

Then type

make this repo ai-ready

Or invoke it explicitly:

ToolInvoke
Claude Code, Cursor, Copilot CLI/ai-ready
OpenAI Codex$ai-ready

When installed as a plugin from a marketplace, Claude namespaces it as /ai-ready:ai-ready.

The skill analyzes your code, CI, tests, docs, and structure, then generates assets customized to your project — not generic templates.

Run it again anytime

The skill is safe to re-run. On the first run, it creates missing assets. On subsequent runs, it audits your existing AI-ready files against the current state of your codebase — flagging drift like outdated build commands, stale repo structure, or new PR review patterns that should become conventions. It never overwrites your files — it suggests updates and lets you decide.

Keeping updated

ToolUpdate
skills CLInpx skills update
GitHub Copilot CLIcopilot plugin update ai-ready
Claude Code/plugin marketplace update johnpapa-ai-ready
Codexcodex plugin marketplace upgrade

Troubleshooting

The agent doesn't use the skill
  1. Restart your agent. Most tools only scan for skills at startup.
  2. Confirm it's installed. Run npx skills list, copilot plugin list, claude plugin list, or codex plugin list depending on how you installed it.
  3. Check you finished both steps. Claude and Codex need a marketplace command and an install command.
  4. Ask for it by name/ai-ready (or $ai-ready in Codex) — to rule out matching problems.
Install fails with a "reference is not a tree" or SHA error

The marketplace entry is pointing at a commit SHA. Plugin installs clone with git clone --branch <ref>, which only accepts a branch or tag, so a raw SHA always fails. The registry entry needs to use a release tag such as v1.3.0. See #26.

Installing directly from this repo (copilot plugin install johnpapa/ai-ready) avoids the problem entirely.

Claude marketplace add fails over SSH

If /plugin marketplace add fails with a Git authentication error, use the full HTTPS URL:

/plugin marketplace add https://github.com/johnpapa/ai-ready

Or tell Git to prefer HTTPS for GitHub:

git config --global url."https://github.com/".insteadOf git@github.com:

Skip what you don't need

Add exclusions to your prompt and the skill will respect them:

make this repo ai-ready but skip CI and issue templates
just generate AGENTS.md and copilot-instructions

Report only

Just want to see where you stand? Ask for a report without generating any files:

how ai-ready is this repo?
score this repo

What to Expect

After you run the skill, you get a full AI-readiness report — analysis, proposed changes, and a projected score. Here's what it looks like for vscode-peacock:

HTML readiness report

🔗 View the interactive version — collapsible sections, responsive layout, works on mobile.

The report shows:

  1. Your Repo Today — current score, what's nailed, what's missing, and why it matters
  2. What I'd Like To Do — proposed files to create (nothing changes until you say so)
  3. If You Accept — projected score with category breakdown
  4. Ready? — offer to create a PR with all the changes

Issue/PR messages generated by this skill always include explicit attribution to the AI Ready skill. It also keeps related docs aligned to repo standards and proactively attempts conflict resolution before opening PRs (or asks when manual help is needed).

📄 Also available as terminal output — same content, rendered in the CLI.

Scoring

Your score is simple: how many of the 12 tracked assets are nailed. That's it — no formulas, no weights.

MedalNameCountWhat it means
🥉Getting Started1–4 of 12Basics are in place but AI agents are mostly guessing
🥈On Track5–7 of 12AI agents can help but they'll miss your conventions
🥇Solid8–10 of 12AI agents follow your patterns and catch most expectations
🏆AI-Ready11–12 of 12AI agents contribute like your best team members

Why

Contributors (human and AI) show up to your repo and don't know the conventions. They submit PRs that miss tests, break patterns, skip docs. You leave the same review comments on every PR. AI agents make this more challenging — they generate PRs faster, but without context, those PRs create more review burden.

It's the same gap from both sides: contributors don't know what maintainers expect, and maintainers keep re-teaching it. This skill closes that gap by generating repo-level configuration that teaches everyone — human and AI — how to work in the repo correctly. It even mines your PR review comments for repeated feedback and turns them into automated conventions. The result: a 45-minute review becomes a 5-minute review.

Built from Real Maintainer Experience

This skill isn't theoretical — it's shaped by John Papa's experience maintaining popular open source projects and repos at large enterprises. The skill is tuned to prioritize what actually reduces review burden: maintenance matrices that catch the files contributors always forget, conventions mined from the PR feedback you're tired of repeating, and CI that catches problems before you have to.

How It Works — GitHub-Native by Default

You shouldn't have to explain to an AI tool that you're in a GitHub repo. This skill assumes it, and leverages everything GitHub already knows about your project.

Auto-Discovery (zero user input)

The skill starts by pulling context directly from GitHub — no questions asked:

What it discoversHowWhy it matters
Repo description, topics, languagesGitHub APIKnows what your project is without reading every file
Community health scoreGitHub APIInstantly knows which config files are missing
ContributorsGitHub APITeam size, contribution patterns
Recent merged PRsGitHub APIUnderstands what typical contributions look like
PR review commentsGitHub APITurns your repeated review feedback into automated conventions
CI/CD workflowsGitHub Actions APIKnows your build/test pipeline
ReleasesGitHub APIUnderstands versioning and release cadence

It then scans your local codebase for deeper details — manifest files, test configs, directory structure, existing AI configuration — and combines both into a complete picture.

PR Review Mining — The Killer Feature

This is the highest-value thing the skill does. It reads your recent PR review threads and looks for repeated feedback — the same comments you leave on every PR:

  • "Please add tests for new features" → becomes a test convention rule
  • "Use the X pattern instead of Y" → becomes a coding convention rule
  • "Don't forget to update the changelog" → becomes a maintenance matrix entry
  • "This breaks on mobile, check responsive layout" → becomes a screen size rule

These mined conventions go directly into copilot-instructions.md. The next AI-generated PR follows those rules automatically. You stop repeating yourself.

What Gets Generated

Every file is customized to your repo's actual language, framework, and patterns — not generic boilerplate. The skill only creates files that don't already exist.

FileWhat It Does
AGENTS.mdProject context for the coding agent — repo structure, build/test commands, architectural decisions, how to add features
.github/copilot-instructions.mdCoding conventions for all Copilot interactions — Chat, completions, PR reviews, CLI. Includes a maintenance matrix of what to update when code changes
.github/workflows/copilot-setup-steps.ymlCloud agent environment setup — runtime versions, dependencies, build steps
.github/workflows/ci.ymlPR validation pipeline — build, test, lint, typecheck. Skips non-code changes (docs, images, etc.)
.github/ISSUE_TEMPLATE/bug-report.ymlStructured bug report form with fields relevant to your project type
.github/ISSUE_TEMPLATE/feature-request.ymlStructured feature request form
.github/PULL_REQUEST_TEMPLATE.mdPR description template with checklist items derived from the maintenance matrix
CHANGELOG.mdKeep a Changelog format, populated from releases/tags if available
.mcp.jsonMCP server config connecting AI agents to your project's databases, APIs, and tools
README ## Contributing sectionOnramp for new contributors — how to fork, build, test, and submit a PR
AI-Ready badge in READMEShields.io badge linking back to this skill — added automatically

Two Layers of PR Quality

The assets this skill generates enable two complementary layers of PR quality — one you get automatically, one you enable:

LayerWhat it catchesHow it works
CI workflow (generated by this skill)Broken builds, failing tests, lint errorsGitHub Actions runs on every PR — validates that the code compiles and tests pass
Copilot code review (you enable this)Convention violations, missing docs/tests, maintenance matrix gapsCopilot reads copilot-instructions.md (generated by this skill) and reviews PRs against your conventions

Together: PRs are validated for correctness (CI) and reviewed for quality (Copilot). This skill generates the inputs for both — the CI workflow and the conventions file that Copilot code review reads.

To enable Copilot code review: go to your repo's Settings → Copilot → Code review and turn it on. Once enabled, every PR is automatically reviewed against the conventions in copilot-instructions.md.

Tested Against

This skill has been validated against a diverse set of repos — courses, applications, VS Code extensions, monorepos, and more. See skills/ai-ready/references/training-repos.md for the full list.

Contributing

Quick Start

  1. Fork this repo and create a branch
  2. Make your changes (skills or docs)
  3. Test locally: copy skills/ai-ready/SKILL.md to ~/.copilot/skills/ai-ready/SKILL.md, start copilot, then say "make this repo ai-ready"
  4. Open a PR

See AGENTS.md for the full contributor guide.

Credits

This skill was strengthened using:

  • Sensei — AI skill quality scorer that evaluates frontmatter, structure, and discoverability. Used to achieve a "High" rating.
  • Agent Skills Spec — GitHub's specification for skill authoring. Used to refactor from 964 lines to a 225-line spec-compliant structure with progressive disclosure.

License

MIT

Contributors

johnpapa

143 commits

Copilot

1 commits

johnpapa/ai-ready

Agent Skill that analyzes your repo and generates the AI-ready configuration coding agents need — AGENTS.md, copilot-instructions, CI, issue templates, and more. Works in Claude Code, GitHub Copilot, Codex, and Cursor.

201

stars

147

commits

Sep 9, 2026

updated

agents
agent-skills
agents-md
ai-ready
claude-code
codex
copilot
copilot-cli
copilot-plugin
cursor
developer-experience
skills

README

AI Ready

AI Ready Version

An Agent Skill that analyzes your repository and generates the configuration files AI agents need to contribute correctly. GitHub-native — it auto-discovers your repo's context, community health, and PR review patterns without you explaining anything.

Works in GitHub Copilot, Claude Code, OpenAI Codex, Cursor, and any other tool that supports the Agent Skills standard.

Quick Start

Any agent, one command

The open skills CLI installs into Claude Code, Codex, Cursor, Copilot, and 70+ other agents:

npx skills add johnpapa/ai-ready

That's it — no per-tool setup. Restart your agent afterward.

Native plugin installs

Prefer your tool's own plugin system? Each of these installs the same skill.

ToolInstall
GitHub Copilot CLIcopilot plugin install ai-ready@awesome-copilot
Claude Code/plugin marketplace add johnpapa/ai-ready
/plugin install ai-ready@johnpapa-ai-ready
OpenAI Codexcodex plugin marketplace add johnpapa/ai-ready
codex plugin add ai-ready@johnpapa-ai-ready
CursorCopy skills/ai-ready/ into ~/.cursor/skills/ai-ready/
Anything elseCopy skills/ai-ready/ into ~/.agents/skills/ai-ready/

Claude and Codex each need two commands — the first registers the marketplace, the second installs the plugin from it.

Copilot CLI installs from the built-in awesome-copilot marketplace. Installing straight from a repo (copilot plugin install johnpapa/ai-ready) still works but is deprecated, so prefer the marketplace form.

~/.agents/skills/ is the vendor-neutral Agent Skills directory that Codex and Cursor both read, so the last row works for most tools.

If a marketplace mirrors this skill, it should point to a release tag such as v1.3.0, not a raw commit SHA.

Then type

make this repo ai-ready

Or invoke it explicitly:

ToolInvoke
Claude Code, Cursor, Copilot CLI/ai-ready
OpenAI Codex$ai-ready

When installed as a plugin from a marketplace, Claude namespaces it as /ai-ready:ai-ready.

The skill analyzes your code, CI, tests, docs, and structure, then generates assets customized to your project — not generic templates.

Run it again anytime

The skill is safe to re-run. On the first run, it creates missing assets. On subsequent runs, it audits your existing AI-ready files against the current state of your codebase — flagging drift like outdated build commands, stale repo structure, or new PR review patterns that should become conventions. It never overwrites your files — it suggests updates and lets you decide.

Keeping updated

ToolUpdate
skills CLInpx skills update
GitHub Copilot CLIcopilot plugin update ai-ready
Claude Code/plugin marketplace update johnpapa-ai-ready
Codexcodex plugin marketplace upgrade

Troubleshooting

The agent doesn't use the skill
  1. Restart your agent. Most tools only scan for skills at startup.
  2. Confirm it's installed. Run npx skills list, copilot plugin list, claude plugin list, or codex plugin list depending on how you installed it.
  3. Check you finished both steps. Claude and Codex need a marketplace command and an install command.
  4. Ask for it by name/ai-ready (or $ai-ready in Codex) — to rule out matching problems.
Install fails with a "reference is not a tree" or SHA error

The marketplace entry is pointing at a commit SHA. Plugin installs clone with git clone --branch <ref>, which only accepts a branch or tag, so a raw SHA always fails. The registry entry needs to use a release tag such as v1.3.0. See #26.

Installing directly from this repo (copilot plugin install johnpapa/ai-ready) avoids the problem entirely.

Claude marketplace add fails over SSH

If /plugin marketplace add fails with a Git authentication error, use the full HTTPS URL:

/plugin marketplace add https://github.com/johnpapa/ai-ready

Or tell Git to prefer HTTPS for GitHub:

git config --global url."https://github.com/".insteadOf git@github.com:

Skip what you don't need

Add exclusions to your prompt and the skill will respect them:

make this repo ai-ready but skip CI and issue templates
just generate AGENTS.md and copilot-instructions

Report only

Just want to see where you stand? Ask for a report without generating any files:

how ai-ready is this repo?
score this repo

What to Expect

After you run the skill, you get a full AI-readiness report — analysis, proposed changes, and a projected score. Here's what it looks like for vscode-peacock:

HTML readiness report

🔗 View the interactive version — collapsible sections, responsive layout, works on mobile.

The report shows:

  1. Your Repo Today — current score, what's nailed, what's missing, and why it matters
  2. What I'd Like To Do — proposed files to create (nothing changes until you say so)
  3. If You Accept — projected score with category breakdown
  4. Ready? — offer to create a PR with all the changes

Issue/PR messages generated by this skill always include explicit attribution to the AI Ready skill. It also keeps related docs aligned to repo standards and proactively attempts conflict resolution before opening PRs (or asks when manual help is needed).

📄 Also available as terminal output — same content, rendered in the CLI.

Scoring

Your score is simple: how many of the 12 tracked assets are nailed. That's it — no formulas, no weights.

MedalNameCountWhat it means
🥉Getting Started1–4 of 12Basics are in place but AI agents are mostly guessing
🥈On Track5–7 of 12AI agents can help but they'll miss your conventions
🥇Solid8–10 of 12AI agents follow your patterns and catch most expectations
🏆AI-Ready11–12 of 12AI agents contribute like your best team members

Why

Contributors (human and AI) show up to your repo and don't know the conventions. They submit PRs that miss tests, break patterns, skip docs. You leave the same review comments on every PR. AI agents make this more challenging — they generate PRs faster, but without context, those PRs create more review burden.

It's the same gap from both sides: contributors don't know what maintainers expect, and maintainers keep re-teaching it. This skill closes that gap by generating repo-level configuration that teaches everyone — human and AI — how to work in the repo correctly. It even mines your PR review comments for repeated feedback and turns them into automated conventions. The result: a 45-minute review becomes a 5-minute review.

Built from Real Maintainer Experience

This skill isn't theoretical — it's shaped by John Papa's experience maintaining popular open source projects and repos at large enterprises. The skill is tuned to prioritize what actually reduces review burden: maintenance matrices that catch the files contributors always forget, conventions mined from the PR feedback you're tired of repeating, and CI that catches problems before you have to.

How It Works — GitHub-Native by Default

You shouldn't have to explain to an AI tool that you're in a GitHub repo. This skill assumes it, and leverages everything GitHub already knows about your project.

Auto-Discovery (zero user input)

The skill starts by pulling context directly from GitHub — no questions asked:

What it discoversHowWhy it matters
Repo description, topics, languagesGitHub APIKnows what your project is without reading every file
Community health scoreGitHub APIInstantly knows which config files are missing
ContributorsGitHub APITeam size, contribution patterns
Recent merged PRsGitHub APIUnderstands what typical contributions look like
PR review commentsGitHub APITurns your repeated review feedback into automated conventions
CI/CD workflowsGitHub Actions APIKnows your build/test pipeline
ReleasesGitHub APIUnderstands versioning and release cadence

It then scans your local codebase for deeper details — manifest files, test configs, directory structure, existing AI configuration — and combines both into a complete picture.

PR Review Mining — The Killer Feature

This is the highest-value thing the skill does. It reads your recent PR review threads and looks for repeated feedback — the same comments you leave on every PR:

  • "Please add tests for new features" → becomes a test convention rule
  • "Use the X pattern instead of Y" → becomes a coding convention rule
  • "Don't forget to update the changelog" → becomes a maintenance matrix entry
  • "This breaks on mobile, check responsive layout" → becomes a screen size rule

These mined conventions go directly into copilot-instructions.md. The next AI-generated PR follows those rules automatically. You stop repeating yourself.

What Gets Generated

Every file is customized to your repo's actual language, framework, and patterns — not generic boilerplate. The skill only creates files that don't already exist.

FileWhat It Does
AGENTS.mdProject context for the coding agent — repo structure, build/test commands, architectural decisions, how to add features
.github/copilot-instructions.mdCoding conventions for all Copilot interactions — Chat, completions, PR reviews, CLI. Includes a maintenance matrix of what to update when code changes
.github/workflows/copilot-setup-steps.ymlCloud agent environment setup — runtime versions, dependencies, build steps
.github/workflows/ci.ymlPR validation pipeline — build, test, lint, typecheck. Skips non-code changes (docs, images, etc.)
.github/ISSUE_TEMPLATE/bug-report.ymlStructured bug report form with fields relevant to your project type
.github/ISSUE_TEMPLATE/feature-request.ymlStructured feature request form
.github/PULL_REQUEST_TEMPLATE.mdPR description template with checklist items derived from the maintenance matrix
CHANGELOG.mdKeep a Changelog format, populated from releases/tags if available
.mcp.jsonMCP server config connecting AI agents to your project's databases, APIs, and tools
README ## Contributing sectionOnramp for new contributors — how to fork, build, test, and submit a PR
AI-Ready badge in READMEShields.io badge linking back to this skill — added automatically

Two Layers of PR Quality

The assets this skill generates enable two complementary layers of PR quality — one you get automatically, one you enable:

LayerWhat it catchesHow it works
CI workflow (generated by this skill)Broken builds, failing tests, lint errorsGitHub Actions runs on every PR — validates that the code compiles and tests pass
Copilot code review (you enable this)Convention violations, missing docs/tests, maintenance matrix gapsCopilot reads copilot-instructions.md (generated by this skill) and reviews PRs against your conventions

Together: PRs are validated for correctness (CI) and reviewed for quality (Copilot). This skill generates the inputs for both — the CI workflow and the conventions file that Copilot code review reads.

To enable Copilot code review: go to your repo's Settings → Copilot → Code review and turn it on. Once enabled, every PR is automatically reviewed against the conventions in copilot-instructions.md.

Tested Against

This skill has been validated against a diverse set of repos — courses, applications, VS Code extensions, monorepos, and more. See skills/ai-ready/references/training-repos.md for the full list.

Contributing

Quick Start

  1. Fork this repo and create a branch
  2. Make your changes (skills or docs)
  3. Test locally: copy skills/ai-ready/SKILL.md to ~/.copilot/skills/ai-ready/SKILL.md, start copilot, then say "make this repo ai-ready"
  4. Open a PR

See AGENTS.md for the full contributor guide.

Credits

This skill was strengthened using:

  • Sensei — AI skill quality scorer that evaluates frontmatter, structure, and discoverability. Used to achieve a "High" rating.
  • Agent Skills Spec — GitHub's specification for skill authoring. Used to refactor from 964 lines to a 225-line spec-compliant structure with progressive disclosure.

License

MIT

Contributors

johnpapa

143 commits

Copilot

1 commits