opencode-instructions-auditor
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outp
SKILL.mdskills/opencode-instructions-auditor/SKILL.md
GitHubOpenCode Instructions Auditor
Audit and improve repository instructions used by OpenCode. Prefer AGENTS.md for durable project guidance and .opencode/opencode.json / opencode.jsonc plus .opencode/agents/ and .opencode/skills/ for supported configuration. Keep CLAUDE.md only when the repository intentionally supports Claude Code too.
Workflow
- Inventory
AGENTS.md, nested instruction files,.opencode/, OpenCode config, skills, agents, commands, and project documentation. - Read the installed OpenCode version and matching official docs before changing version-sensitive syntax.
- Identify duplicate, contradictory, stale, untestable, overly broad, or tool-specific instructions. Separate project facts from rules and guesses.
- Preserve valid project decisions. Do not replace them with generic conventions or invent architecture.
- Propose a concise change list with exact paths and expected effects. Ask before broad rewrites or deleting content.
- After approval, make focused edits; validate frontmatter, JSON/JSONC syntax, relative links, script paths, and skill directory/name consistency.
- Report changes, checks run, failures, and unresolved assumptions.
Audit criteria
- Correct OpenCode paths and supported frontmatter/config keys
- Clear precedence and scope (global vs project vs nested directory)
- Explicit workflow: inspect → plan → execute → verify → report
- No unsupported Claude Code tool names or assumed hooks in OpenCode-only instructions
- Least privilege for tools, permissions, and MCP access
- Test/build commands grounded in repository documentation
- Instructions do not encourage destructive commands without confirmation and backup