ar-install

Adopts a repository for AI assistants by extracting codebase conventions into per-repo config and coding rules.

1|2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-install-mahsanamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ar-install
Source: https://github.com/mahsanamin/agentic-repos/tree/main/.claude/commands/ar-install
Command: npx skills add https://github.com/mahsanamin/agentic-repos --skill ar-install-mahsanamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding assistants produce generic code that ignores a team's real conventions because nothing documents how the team works in a form the assistant can read. This Skill makes a repository agent-ready by writing its per-project config and rules layer, extracted from the actual codebase. ## Core Features & Use Cases - Convention Extraction: Maps the codebase and extracts its real conventions into coding rules under the configured standards location, citing real files and project idioms rather than generic templates. - Config Generation: Writes config_hints.json, AGENTS.md, .claude/skill.config, autonomous .claude/settings.json permissions, CLAUDE.md, PR/commit templates, and optional ERD documentation. - Stack Detection: Detects the project stack from positive evidence (e.g., Android vs Spring Boot vs generic JVM) and applies only the applicable framework rule directories. - Use Case: Point it at an unadopted repository, and it creates an install branch, explores the code, writes the full config and rules layer, verifies there is no contamination, and reports next steps. ## Quick Start Say "ar-install" or "make this repo agent-ready" and provide the full path to your target project when asked.

Frequently Asked Questions about ar-install

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

FAQPage Schema
How do I make a repository agent-ready for AI coding assistants?▼

Run ar-install and provide the full path to the target project. It creates an install branch, extracts the codebase's real conventions into coding rules, and writes config_hints.json, AGENTS.md, settings, and templates on that branch.

What files does ar-install write into a project?▼

It writes config_hints.json, AGENTS.md, .claude/skill.config, an autonomous .claude/settings.json with permissions only, CLAUDE.md pointing to AGENTS.md, PR and commit templates, extracted coding rules, and an optional ERD if a database is detected.

Does ar-install work with Claude Code and Codex?▼

Yes, the generated config layer serves both harnesses from the same files. Codex support is optional and writes only .codex/config.toml plus a git-guard hook after asking, with a manual /hooks trust step required.

Can I run ar-install on a repo that already has config_hints.json?▼

No, ar-install stops if .claude/config_hints.json already exists and directs you to use ar-upgrade instead. It is designed only for first-time adoption of a repository.

Why does ar-install fail with a global layer missing error?▼

The ar-* skills and agentic-devkit must be installed once per machine via install.sh from the framework root before adoption. ar-install only writes the per-repo layer and never installs the global procedure itself.

How does ar-install detect the project stack?▼

It uses positive-evidence detection, requiring concrete signals like framework imports or plugin declarations rather than build tools alone. For example, Gradle with Kotlin detects as android or jvm-generic, not java-spring-boot, unless Spring Boot evidence exists.