principle-preserve-unrelated-work
WHEN a diff, commit or git action could touch anything outside the request; NOT for deciding whether an action is authorised at all or for syncing with a base branch; keeps unrelated behaviour, worktree changes, data and the index as found.
- License 许可
- MIT
- 所属仓库
- mintuz/skills
- 最近更新
- 2026-11-13
- Stars
- ★ 35
- Forks
- 7
01 前言 Front Matter
- name
- principle-preserve-unrelated-work
- description
- WHEN a diff, commit or git action could touch anything outside the request; NOT for deciding whether an action is authorised at all or for syncing with a base branch; keeps unrelated behaviour, worktree changes, data and the index as found.
03 SKILL.md 正文
Preserve unrelated work
Leave behaviour and edits you were not asked to change.
- Before writing, read the worktree and index. Treat every change you did not make as someone else's work, even in the file you are editing.
- The scope is the whole requested change and the edits it requires: when the request changes an interface, the new interface and the updated callers are in scope. Outside that scope, preserve supported behaviour (outputs, side effects, errors, ordering, concurrency, persistence, compatibility) and user data. Reformatting, renames and tidy-ups elsewhere are separate changes, proposed rather than bundled.
- Leave others' worktree changes and the index as found. Stage and commit only your own hunks, and only when asked; when you share a file with someone's edits, select your hunks rather than the whole file. Stash, reset, checkout and discard stay off others' changes.
- Before handing over, compare your diff and the index with the starting state. Revert each incidental change, or justify it in the report.
Distinct from: principle-stay-in-scope (whether an action is authorised at all), principle-update-the-base-deliberately (starting from or syncing with a base), principle-clean-up-what-you-started (tearing down resources a run created).
Done: unrelated behaviour, worktree changes and the index are unchanged, or each change is justified.
04 同仓库更多 Skills
xstate
WHEN React state changes in response to an external answer — async submit, in-flight or loading flags, retries, cancellation, polling, optimistic updates, stale responses — or to an interaction with an interruptible middle, such as a drag or a gesture; or WHEN building, reviewing, testing, or visualising XState 5 actors and @xstate/react integrations; NOT for a value one event sets completely, such as a text draft, a focus flag, or a plain open and closed toggle; models typed lifecycles and renders legal Mermaid stateDiagram-v2 charts.
web-design
WHEN refining UI layout, typography, color, or polish; NOT code implementation; provides concise principles for intentional, legible design.
tailwind
USE WHEN writing, fixing or reviewing styling in a project that uses Tailwind CSS, even a one-class change or a request that does not name Tailwind: colours, focus rings, spacing, class names chosen by a prop, map or CVA variants, theme tokens and dark mode in the Tailwind stylesheet or tailwind.config, setup or upgrades (if unsure whether the project uses Tailwind, check package.json or the main stylesheet first); NOT WHEN writing plain CSS or Sass in a project without Tailwind; produces class names Tailwind can find, syntax for the installed major version, visible focus indicators, and no unrequested dependency or invented brand value.
refactoring
WHEN you need a plan to refactor, restructure, or clean up working code and the test result is known, either green or a recorded failing set; NOT for new feature delivery or any behavior change; reversible-baseline safety with prioritized improvements.
react
USE WHEN changing the logic, data, props, state, Effects or rendered text of a React component, hook or page, even a one-line change; NOT WHEN the request is styling only (class names, Tailwind, CSS, dark mode, spacing, shadows) or tests only, or when it models submit, in-flight, loading, retry or failure states, even for a named React form (xstate covers that, including its React wiring); applies React 19 composition, state, Effect, structure, API and performance rules with only the project's installed libraries.
react-testing
USE WHEN writing, fixing or reviewing a React Testing Library test for a component, hook or context provider, even one small test, or when asked for an end-to-end journey inside a Vitest or React Testing Library suite; NOT WHEN changing the component itself (react), testing XState actors or @xstate/react (xstate), or writing a Playwright or Cypress test; covers renderHook, providers, async results, forms and false-pass anti-patterns, and declines end-to-end journeys with the testable slices.