lee-spec-kit 0.6.27 → 0.6.28
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +135 -20
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
- package/templates/en/common/agents/skills/create-pr.md +4 -2
- package/templates/en/common/features/feature-base/tasks.md +1 -1
- package/templates/ko/common/agents/skills/create-pr.md +4 -2
- package/templates/ko/common/features/feature-base/tasks.md +1 -1
package/package.json
CHANGED
|
@@ -24,8 +24,10 @@ Always run this checklist in Pre-PR review. Treat it as the minimum baseline, th
|
|
|
24
24
|
4. Run related test/verification commands (or explicitly record why they were not run).
|
|
25
25
|
5. Run `npx lee-spec-kit pre-pr-review <feature-ref>` to record review notes in `decisions.md` and sync `Pre-PR Evidence/Decision`.
|
|
26
26
|
6. `Pre-PR Evidence` should point to a real existing path. (default: `workflow.prePrReview.evidenceMode=path_required`)
|
|
27
|
-
7. `Pre-PR
|
|
28
|
-
8.
|
|
27
|
+
7. In `decisions.md`, include a `Pre-PR Review Log` section with non-placeholder `Summary` and `Decision` entries.
|
|
28
|
+
8. In code-review stage, keep `PR Review Evidence/Decision` aligned with `decisions.md` by adding a `PR Review Log` section with `Summary` and `Decision`.
|
|
29
|
+
9. `Pre-PR Decision` must use `decision: approve|changes_requested|blocked ...` (or `결정: ...`).
|
|
30
|
+
10. Ensure the final decision is `approve` before moving to PR creation.
|
|
29
31
|
|
|
30
32
|
---
|
|
31
33
|
|
|
@@ -31,7 +31,7 @@
|
|
|
31
31
|
- PR creation requires final decision `approve`
|
|
32
32
|
- Follow `agents/skills/create-pr.md` (`Pre-PR Baseline Checklist`) as the default baseline
|
|
33
33
|
- **PR Review Evidence**: -
|
|
34
|
-
- Example:
|
|
34
|
+
- Example: `summary: ...` (or `요약: ...`), or `docs/features/F001-foo/decisions.md` with `PR Review Log`
|
|
35
35
|
- **PR Review Decision**: -
|
|
36
36
|
- Record why/how review comments were addressed as `decision: ...` (or `결정: ...`)
|
|
37
37
|
|
|
@@ -24,8 +24,10 @@ Pre-PR 리뷰에서 항상 수행하는 최소 기준입니다. 가능한 경우
|
|
|
24
24
|
4. 관련 테스트/검증 명령을 실행합니다. 실행하지 못했다면 사유를 명시합니다.
|
|
25
25
|
5. `npx lee-spec-kit pre-pr-review <feature-ref>`를 실행해 리뷰 내용을 `decisions.md`에 기록하고 `PR 전 리뷰 Evidence/Decision`을 동기화합니다.
|
|
26
26
|
6. `PR 전 리뷰 Evidence`는 실제 존재하는 문서 경로를 사용합니다. (`workflow.prePrReview.evidenceMode=path_required` 기본)
|
|
27
|
-
7. `PR 전 리뷰
|
|
28
|
-
8. PR
|
|
27
|
+
7. `decisions.md`에 `Pre-PR Review Log`(또는 `PR 전 리뷰 로그`) 섹션을 두고 `Summary`/`Decision`을 placeholder 없이 기록합니다.
|
|
28
|
+
8. 코드리뷰 단계에서도 `PR 리뷰 Evidence/Decision`과 `decisions.md`를 동기화하고 `PR Review Log`(또는 `PR 리뷰 로그`)의 `Summary`/`Decision`을 기록합니다.
|
|
29
|
+
9. `PR 전 리뷰 Decision`은 `결정: approve|changes_requested|blocked ...` (또는 `decision: ...`) 형식을 사용합니다.
|
|
30
|
+
10. PR 생성 단계로 이동하기 전 최종 Decision이 `approve`인지 확인합니다.
|
|
29
31
|
|
|
30
32
|
---
|
|
31
33
|
|
|
@@ -31,7 +31,7 @@
|
|
|
31
31
|
- PR 생성 전 최종 통과 기준은 `approve`
|
|
32
32
|
- 기본 베이스라인으로 `agents/skills/create-pr.md`(`Pre-PR 기본 체크리스트`) 기준을 따르세요
|
|
33
33
|
- **PR 리뷰 Evidence**: -
|
|
34
|
-
- 예:
|
|
34
|
+
- 예: `요약: ...`(또는 `summary: ...`), 또는 `PR Review Log`가 있는 `docs/features/F001-foo/decisions.md`
|
|
35
35
|
- **PR 리뷰 Decision**: -
|
|
36
36
|
- 리뷰 지적사항을 왜/어떻게 반영했는지 `결정: ...`(또는 `decision: ...`) 형식으로 기록
|
|
37
37
|
|