Imported from hasansezertasan/infra-copilot (AGENTS.md). Install upstream with npx skills add hasansezertasan/infra-copilot. Copyright stays with the author.

infra-copilot — agent context

This repository is a set of agent instructions. When you are asked to change it, the most likely way to get it wrong is to edit the wrong copy of a file.

Rule 1: do not edit generated files

skills/, commands/, .claude-plugin/, and .codex-plugin/ are generated from .ai-rulez/. They are the obvious files to open — skills/setup/SKILL.md looks like the skill — and editing them is silently undone by the next make generate.

Before editing any file under those paths, check .ai-rulez-generated.json. If the path is listed (34 are), edit its source under .ai-rulez/ instead, then run make generate.

Most generated files carry an AI-RULEZ :: GENERATED FILE — DO NOT EDIT header, but eleven of the 34 do not — the three JSON manifests, config.md.example, decisions.md.example, steps.yaml, and the five shell scripts checks/status-check-context.sh, checks/hcp-apply-scope.sh, checks/hcp-bootstrap-workspaces.sh, checks/leaf-cloud.sh, and checks/hcp-current-plan.sh, where a Markdown comment would not be valid. Absence of the header is not evidence a file is safe to edit. The manifest is the authority; the header is only a convenience.

File resolution

Rule 2: run make check

Never invoke npx ai-rulez, python3 scripts/validate.py, or the skills installer directly in documentation, in a commit's verification step, or in the Linux CI job. make check is CI parity.

One deliberate exception: the windows-paths job in .github/workflows/check.yml calls python scripts/validate.py and the tests directly, because make is not guaranteed on windows-latest. That job exists to prove paths stay portable, not to be CI parity. Leave it as it is.

Architecture, in one paragraph

Four action skills — setup, import, add, status — are thin routers over one hub skill, infra-copilot, whose references/ directory owns the behavior: steps.yaml (a phase-tagged step manifest with a check per step), protocol.md (the actor model, the handoff block, the resume scan, preflight), provider deep-dives, and runbooks. Host packages are adapters and must never become a second behavioral authority. State is never assumed: every run re-derives it by executing each step's check.

Conventions

• Conventional Branch names, Conventional Commits.
• No AI attribution in commits, PR titles, or bodies.
• Behavior in .ai-rulez/skills/; host-specific values in adapters only.

See CONTRIBUTING.md for the full loop and docs/roadmap.md for what is deliberately unbuilt.