From d6022fcb79a7ecf0f6d82882e6ed8a95f49240d3 Mon Sep 17 00:00:00 2001 From: David Kaya Date: Sun, 22 Mar 2026 18:25:14 +0100 Subject: [PATCH] docs: require cleanup of obsolete fixes Clarify in the agent guidelines that experiments, workarounds, helpers, and test paths that do not end up in the final correct solution must be removed before handoff. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 0babfbd..e8c175c 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -41,6 +41,7 @@ These instructions apply to any automated or semi-automated agent working in thi - Keep commits atomic. Each commit should represent one logical change and use a Conventional Commit message such as `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, or `chore:`. - Treat tests as part of the implementation, not as follow-up work. Every fix, behavior change, and new feature must be covered by tests, and the relevant test suite must pass before the work is considered complete. - Do not ship quick fixes, hacks, or "temporary" patches as final solutions. Take the time to understand the problem, plan the change, and implement a maintainable solution that fits the codebase cleanly. +- Remove code that is no longer necessary before handing work off. If an experiment, workaround, hotfix, helper, or test path does not end up being part of the final correct solution, delete it rather than leaving dead or misleading code behind. - Apply the same quality bar to feature work. Think through scope, edge cases, integration points, and long-term maintainability before implementing. - When adding or updating dependencies, use the latest stable version available. If a non-latest version is required for compatibility, document the reason explicitly in the change.