update-project-guidance

Generate or refresh the repository-root AGENTS.md guidance file for AI agents.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill update-project-guidance-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-project-guidance
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/update-project-guidance
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill update-project-guidance-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents need project-specific context to work effectively, but writing and maintaining an AGENTS.md file is tedious and it drifts out of date as the codebase evolves. This Skill audits the repository and produces a concise, accurate AGENTS.md, or reconciles an existing one against current reality. ## Core Features & Use Cases - Authoring path: Explores package metadata, configs, and docs to draft a new AGENTS.md from a standard skeleton when no guidance exists. - Refresh path: Audits every checkable claim in an existing AGENTS.md against the codebase, records a verdict ledger, and emits a minimal change list of repairs, removals, relocations, and additions. - Legacy migration: Migrates content from older locations like .agents/PROJECT.md into the repo-root file and wires up the Claude Code include. - Use Case: After a monorepo restructure, run the refresh path to detect that a documented directory listing and command have drifted, then apply only the approved edits while leaving everything else byte-identical. ## Quick Start Ask the agent to update the project guidance for this repository and approve the draft or change list it presents.

Frequently Asked Questions about update-project-guidance

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

FAQPage Schema
How do I create an AGENTS.md file for my repository?

Run the update-project-guidance skill on a repo with no existing guidance and it takes the authoring path: it reads package.json, workspace configs, and docs, classifies findings, and drafts an AGENTS.md from a standard skeleton. Nothing is written until you approve the draft.

How do I update an outdated AGENTS.md file?

The refresh path audits every checkable claim in your existing AGENTS.md against the codebase, records a ledger of holds, drifted, and unchecked verdicts with evidence, then emits a change list of repairs, removals, relocations, and additions. Only approved edits are applied.

Does AGENTS.md work with Claude Code and other AI coding tools?

Yes. Rovo Dev reads the repo-root AGENTS.md directly, and Claude Code loads it through a raw include in .claude/CLAUDE.md pointing to @../AGENTS.md. The skill creates or repairs that include so one file serves every harness.

What should go in AGENTS.md versus a package README?

AGENTS.md holds ambient guidance: project-specific facts an agent gets wrong without, such as required bootstraps and non-obvious gotchas. Reference material needed only occasionally belongs in the owning package's README or docs, and anything already covered by global guidance is omitted.

What happens to legacy .agents/PROJECT.md files?

Content from legacy files like .agents/PROJECT.md or .agents/AGENTS.md is migrated into the repo-root AGENTS.md, with any relative includes re-derived for the new location. The skill recommends removing or archiving the old files but never deletes them without explicit approval.