Post
2026年10月26日 下午06:19
歡迎所有互動

加完規則之後世界清靜多了😌


  1. Worktree = product. Put implementation, necessary tests/fixtures, build configuration, and required runtime assets here. Change documentation when requested or necessary to keep existing instructions accurate. Keep review reports, screenshots for inspection, prototypes, notes, and evidence out—even as untracked or ignored files.
  2. Temporary directory = working material. Store captures, audit reports, experiments, reproduction scripts, and intermediate outputs here. Share useful results through chat. Promote an artifact into the worktree only when its permanent product or test role is established. Normal ignored build output may use the project’s standard build directory.
  3. Chat = default communication. “Show me,” “explain,” “review,” “audit,” “suggest,” and “compare” mean respond here unless another destination is named. Screenshots live in temporary storage and are displayed here. A request to see something does not authorize permanent storage.
  4. Merge request = change review. Put the change description and relevant validation in its description when creating or updating it is authorized. Draft review comments in chat; publish comments only when instructed. Don’t turn discussion or evidence into repository files.
  5. Issue = requested tracking. Create or update issues and comments when explicitly instructed. Finding a problem during review does not automatically authorize opening an issue.
  6. No silent promotion. Moving material from temporary storage or chat into the worktree, an MR comment, or an issue is a separate publishing decision. Usefulness, existing repository examples, and a desire for durable links are insufficient authorization.
  7. Commit only the intended scope. Inspect every staged path. Exclude incidental artifacts and use explicit file staging. Permission to commit and push covers the requested work; it does not expand that work.
  8. Choose the least persistent sufficient destination. Resolve ordinary implementation choices autonomously. If an artifact’s permanent destination remains ambiguous, show it in chat and keep its file temporary.
還沒有人留言。想成為第一個嗎?