Skip to content

Adonis0123/adonis-skills / skills/agent-practice-audit

agent-practice-audit

Flagged

Score how someone uses coding agents (Claude Code, Codex, Grok and WorkBuddy session logs, instruction files, hooks, permissions, Codex config) against practices quoted from official vendor docs, and write a local HTML report with coverage, trend and suggestions; also refresh or verify that practice list from official docs with multi-model consensus. Use when the user asks how far their agent usage is from official practice, wants an agent usage check-up or grade, or wants the practice list refreshed, its links checked, or either run on a schedule. Chinese triggers: Agent 用法体检、对照官方最佳实践、我的 agent 用得对不对、给 agent 用法打分、更新最佳实践清单. Not for whether a tool, MCP or skill is worth keeping (dev-environment-roi-audit), for writing or reviewing one CLAUDE.md or AGENTS.md, for general best-practice questions, or for Cursor or Gemini CLI logs, which it does not read. Never edits the user's config.

FileKindSize
SKILL.mdskill md18.3 KB
assets/default-config.jsonconfig352 B
assets/img/hero.webpbinary106.5 KB
assets/img/nika-wordmark-white.svgother490 B
assets/img/nika-wordmark.svgother490 B
assets/report-template.htmlother41.2 KB
evals/evals.jsonconfig844 B
evals/trigger-eval-set.jsonconfig1.6 KB
references/audit-files.mdmarkdown32.2 KB
references/changelog.mdmarkdown7.2 KB
references/practices.jsonconfig37.3 KB
references/scheduling.mdmarkdown11.9 KB
references/sources.mdmarkdown6.5 KB
references/sources/cc-art-loops.mdmarkdown1.7 KB
references/sources/cc-art-maximizing-sessions.mdmarkdown1.9 KB
references/sources/cc-art-opus-5-5-context.mdmarkdown1.4 KB
references/sources/cc-art-sdlc-playbook.mdmarkdown1.9 KB
references/sources/cc-art-steering.mdmarkdown1.9 KB
references/sources/cc-art-verification-loops.mdmarkdown1.6 KB
references/sources/cc-best-practices.mdmarkdown3.0 KB
references/sources/cc-common-workflows.mdmarkdown1.7 KB
references/sources/cc-costs.mdmarkdown2.3 KB
references/sources/cc-memory.mdmarkdown1.7 KB
references/sources/codex-agents-md.mdmarkdown1.5 KB
references/sources/codex-best-practices.mdmarkdown2.6 KB
references/sources/codex-non-interactive.mdmarkdown1.3 KB
references/sources/codex-sandboxing.mdmarkdown1.4 KB
references/sources/cursor-agent-best-practices.mdmarkdown1.8 KB
references/verify-prompt.mdmarkdown4.6 KB
scripts/aggregate.pyscript22.3 KB
scripts/audit_common.pyscript8.6 KB
scripts/build_report.pyscript30.8 KB
scripts/check_practices.pyscript24.8 KB
scripts/config_scan.pyscript28.3 KB
scripts/consensus.pyscript38.1 KB
scripts/digests.pyscript10.2 KB
scripts/export_metrics.pyscript10.3 KB
scripts/extract.pyscript42.5 KB
scripts/prejudge.pyscript41.8 KB
scripts/run_audit.pyscript3.8 KB
scripts/safe_output.pyscript2.0 KB
scripts/test_agent_practice_audit.pyscript81.1 KB
scripts/test_consensus_run.pyscript26.9 KB
scripts/test_measurement.pyscript68.7 KB
scripts/test_prejudge.pyscript24.2 KB

references/sources/cc-best-practices.md

View on GitHub
---
slug: cc-best-practices
title: Best practices for Claude Code
publisher: Anthropic
url: https://code.claude.com/docs/en/best-practices
fetchedAt: 2026-10-31
lastVerifiedAt: 2026-11-11
linkStatus: ok
finalUrl:
---

# Best practices for Claude Code

## Summary

- Defaults already work for a first prompt; extra setup matters when the project holds knowledge or rules that the code alone does not reveal.
- Write specific prompts, and brainstorm or interview with Claude before building so it does not guess what you meant.
- Keep `CLAUDE.md` short and focused; scope narrow rules to one part of the codebase and move team procedures into skills.
- Put the command that runs tests or checks in `CLAUDE.md`, because a runnable check is the most useful single instruction.
- Give Claude a check that returns pass or fail, and ask for evidence such as command output or screenshots.
- A Stop hook can enforce that a check passes before Claude is allowed to finish.
- Rules without exceptions belong in hooks, deny rules or managed settings, not in prose instructions that Claude may weigh against other things.
- Deny rules apply in every permission mode, so secrets such as `.env` files should be blocked there.
- Keep the enforced set small; a very long list of hard rules usually means many are really preferences.
- Use `/clear` between unrelated tasks, and restart with a better prompt after repeated failed corrections instead of arguing further.
- Choose model, effort and permission mode deliberately, and remember that subagents add their own cost.
- For unattended work, run Claude from scripts with turn and budget limits, schedule runs, and give parallel work separate checkouts.

## Cited quotes

- "/clear between unrelated tasks. It costs nothing…" (ctx-clear-between-tasks)
- "after two failed corrections run /clear and write a better prompt instead of a third" (ctx-clear-between-tasks)
- "Set model: haiku in a subagent's definition if its work is simple" (ctx-custom-subagents)
- "If something has to happen every time, make it a hook, a deny rule, or a managed setting." (safe-hooks-for-musts)
- "Whatever the scope, keep the enforced set small. … If you ever find yourself at forty of them, most are probably preferences" (safe-small-enforced-set)
- "deny rules hold in every permission mode, including auto and bypassPermissions, which is exactly why the .env rule belongs there" (safe-deny-secrets)
- "the single most useful line in your CLAUDE.md is the command that runs it." (doc-test-commands)
- "Ask Claude to interview you instead" (plan-interview)
- "Give Claude something it can run that comes back pass or fail." (verify-runnable-checks)
- "ask Claude for evidence: the command it ran and its output, or the screenshot." (verify-runnable-checks)
- "When you have separate pieces of work going at once, give each its own checkout so the edits can't collide." (auto-worktrees)
- "runs once and exits, which is how Claude Code ends up in CI jobs, git hooks, and shell loops." (auto-headless)
- "What stops it? --max-turns, --max-budget-usd, a spend limit." (auto-headless-limits)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall