chore(repo): move agent assets under agents/ and add repo AGENTS.md #12
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/move-agent-assets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
AGENTS.md,commands/, andskills/intoagents/, so the repo root holds only tooling and CI config. Pure renames — 107 files at 100% similarity, no content changes.mise.tomltasks,.forgejo/workflows/skills-scan.yaml, andscripts/check_skill_versions.py.AGENTS.mdfor agents working in this repo: layout, the mise check/validate/scan tasks, and the SkillSpector/Aguara baseline-refresh procedure — relocated out ofagents/skills/README.md.README.mdas a short human-facing intro with a layout table.Why
The repo root mixed the consumable assets with the tooling that checks them, and there was no repo-level guide for agents — the scanning procedure lived inside the skills README, where only agents that opened that file would find it.
Notes
agents/AGENTS.md(personal global agent instructions, deployed to~/.agents/AGENTS.md) is a different document from the new rootAGENTS.md; both files say so to avoid confusion..skillspector-baseline.yamland.aguara-baseline.jsonbaselines are scan-root relative, so they needed no changes — only the task and CI paths did.~/.agents/skills/*,~/.config/opencode/commands/state-update.md) were relinked; they are outside version control.Verification
mise run check-skill-versions— PASS (30 skills havemetadata.version)mise run validate-skills— PASSmise run scan-skills— PASS (skillspector: 0 unbaselined; aguara: 27 findings, 0 new)