docs(agents): scale local verification to change risk

.agents/skills/issue-fix/SKILL.md

@@ -9,6 +9,14 @@ The reported case is one sample of a defect class. A fix that only makes the
 screenshot go away is not done: the next question is always "does this break for other
 languages / platforms / entry points too?". Answer that before anyone asks.
 
+Scale the workflow to the risk. For an obvious, low-risk CSS or copy fix, inspect
+the cause and nearby shared styles, make the focused edit, check formatting and
+verify the affected UI. Run existing targeted tests only when they cover a plausible
+regression; do not add implementation-mirroring tests or default to full-suite tests,
+E2E, builds, typechecking or dependency analysis. Reuse completed checks while the
+diff is unchanged. A brief finding and verification note is enough; skip the formal
+sibling table. Follow `AGENTS.md` for broader changes and create a PR when requested.
+
 ## 1. Read and reproduce
 
 - `gh issue view <n> --comments` (repo `l0ng-ai/openidea`). Read attached logs/screenshots

AGENTS.md

@@ -84,7 +84,13 @@ Shared agent skills live in `.agents/skills/` (`.claude/skills/` links to them):
 
 ## Before opening a PR
 
-Run what CI runs for the parts you touched:
+Scale local verification to the change. For low-risk CSS-only or copy-only changes,
+check the diff and formatting of touched files; use existing targeted tests when they
+cover a plausible regression, and verify visible changes in the running app. Reuse
+completed checks when the diff has not changed. Do not default to full tests, E2E,
+builds, typechecking or dependency analysis for these changes; CI runs the full suite.
+
+For behaviour, shared infrastructure or broader changes, run the applicable CI checks:
 
 - Rust: `cargo fmt --all --check`, `cargo clippy --workspace --all-targets -- -D warnings`,
   `cargo nextest run --workspace`. After changing IPC types, run `pnpm gen:bindings` and