From 6581685feafa2662488d13790110405abed0eaeb Mon Sep 17 00:00:00 2001 From: bowenliang123 Date: Thu, 15 Oct 2026 14:23:49 +0800 Subject: [PATCH] fix(docs): clarify regex usage in test command for iteration --- AGENTS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index c4030cf..855676e 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -21,7 +21,7 @@ A DeepSeek Harness plugin for context insight, actions, and management. - User experience, features, and especially the data accuracy and integrity are the top priority. Never sacrifice them for code refactors, performance, or any other reason. Dive deep and run real tests to verify the correctness of every change. - Reuse the classes, utilities, styles, style tokens, events, presets, and lifecycles that DeepSeek Harness already provides. - Keep code and tests small, loosely coupled, and modular; avoid duplication. -- After updating tests, firstly run `pnpm exec vitest run tests//.spec.ts -t ""` to iterate on the touched test cases. +- After updating tests, firstly run `pnpm exec vitest run tests//.spec.ts -t ""` (regex, use `"a|b"`) to iterate on the touched test cases. - Ensure every source code file or test code file has less than 1000 lines. - Add comments only for major decisions or significant value, and update or delete outdated ones when modifying the code. - Comments guideline: