wangsli和Claude Sonnet 5
c4025083af
2026-09-09 本地已验证完成、待交审的治理修复，一直未提交： - 6 个 skill（trellis-before-dev/brainstorm/check/continue/finish-work/start） 统一改为"先检查当前和直接相关既有任务，复用优先于新建"，取代原来"复杂任务 先请求新建 task"的默认动作；新增 worktree/active-task 一致性校验步骤。 - project-governance.md 新增两节：Task Reuse（任务复用判据）、Active Task And Worktree Alignment（激活任务与实际执行 worktree 一致性检查，防止跨 worktree 会话把上一个任务的 workflow-state 当成当前任务）。 - workflow.md 的 Request Triage / Parent-Child 章节、no_task 面包屑同步改写。 本地已过 task validate、check-trellis-governance.mjs、check-process-contract.mjs、 audit-docs.mjs、git diff --check；无业务代码改动。 Co-Authored-By: Claude Sonnet 5 <[email protected]>
18 行
1.9 KiB
Markdown
18 行
1.9 KiB
Markdown
---
|
|
name: trellis-check
|
|
description: "Verify the current task diff against its acceptance criteria and affected-layer contracts. Use after implementation or before an authorized commit, not for unrelated repository cleanup."
|
|
---
|
|
|
|
# Task-Scoped Quality Check
|
|
|
|
Verify the active task and actual validation worktree match the task/diff being checked; run official `task.py current --source` again if scope or cwd changed. Checks from the main checkout do not validate an edited isolated copy. Follow project-governance.md → Active Task And Worktree Alignment; record worktree and candidate separately from deployment and independent review.
|
|
|
|
1. Identify files changed by this task. Git dirty state is evidence, not permission to include other work.
|
|
2. Read acceptance criteria and applicable quality contracts not already loaded. Check the complete task diff, not only the last chunk.
|
|
3. Run the minimum meaningful checks: targeted regressions for behavior changes, relevant syntax/type/build checks for affected layers, and governance/reference checks for rules. Expand for shared contracts and cross-layer risks.
|
|
4. Verify permissions, state transitions, error handling, data flow and tests when affected. Review abstractions and fallback behavior only where the task changes them.
|
|
5. Fix task-caused failures and rerun affected checks. Report pre-existing failures separately; do not repair unrelated business code. Reuse passing checks whose inputs remain unchanged.
|
|
6. Report what passed, failed, was not run and why. Distinguish static checks, runtime tests, independent review and public deployment. Never claim a separate reviewer when only the main session checked.
|
|
|
|
Run one final task-wide acceptance pass before handoff. Do not repeat full-repository tests each iteration or require deployment for pure rules, documentation or local tooling. Capture reusable contracts in the existing spec only when they add value.
|