Skip to content

AGENTS.md

Latest commit

 

History

History
31 lines (30 loc) · 2.22 KB

AGENTS.md

File metadata and controls

31 lines (30 loc) · 2.22 KB
Raw

Repository instructions

  • Use English for all repository content. Match the user's language in conversation.
  • Preserve user changes. Do not modify the host's Homebrew installation in tests; use isolated environments. Follow user authorization for commits and publishing.
  • After completing and verifying repository changes, commit the task's changes using Conventional Commits without asking again. Preserve unrelated user work; report blockers instead of bypassing checks or signing. Do not push or publish unless separately requested. Do not create empty commits for discussion-only tasks.
  • Product behavior follows docs/design.md. Keep execution unavailable until verified artifacts and the complete dependency plan are bound to execution. Unknown evidence never means success; emergency mode waives only bounded age conditions, never integrity, trust, or plan binding.
  • For ownership/import changes, read architecture; for security-sensitive behavior, read threat model; for dependencies or input handling, read implementation rules.
  • Before implementing or changing a security feature, follow Homebrew integration: inspect upstream support, establish its actual guarantees, and prefer reuse with justified gap filling. Homebrew compromise is out of scope; previews and duplicate checks do not prove execution binding. Begin product work with the integration probes in the design.
  • Use .agents/skills/brewwarden-change for behavior/boundary changes and .agents/skills/brewwarden-review for consequential reviews.
  • Test behavior with realistic failure cases. Architecture fixtures must resolve their target packages and fail for the intended forbidden edge. Do not add tests that merely mirror documentation or implementation.
  • Run ./scripts/verify.sh; report actual checks and limitations. See CONTRIBUTING.md for commits, hooks, and file inclusion.
  • Keep current rules in one authoritative document. Put historical investigations and decision rationale in docs/archive/; do not load or link them from routine entry points unless the task requires revisiting that decision.