메뉴
Land a finished product task — prune the working files (keep spec.md), then finalize the draft PR into ready-for-review.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/blockscout/frontend --skill finalize-task명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | finalize-task |
| description | Land a finished product task — prune the working files (keep spec.md), then finalize the draft PR into ready-for-review. |
| disable-model-invocation | true |
Land a task whose every progress.md box is checked. Two steps: prune the disposable working files, then
finalize the PR. Why only spec.md survives — the decomposition is preserved in git history, one commit per
ticket — is in ../../tasks/concepts.md.
Confirm the task is done: every box in progress.md is checked. If any is unchecked, stop and report which
ticket is unfinished — there is nothing to land yet.
Then delete the disposable files, keeping only spec.md in the task folder:
tickets/ — the whole directory, review files included.progress.md.questions.md.review.md / review-<tag>.md, if a task-level review ran in md mode.Commit the deletions on the feature branch as the task's final commit — a plain descriptive subject, the
repo's Co-Authored-By trailer, no #issue reference. Pruning before the PR is finalized is what lets
the whole-task review read the spec and the diff without any ticket files.
Hand off to the create-pr skill in finalize-draft mode (Mode B).
Step-by-step checklist for adding a new NEXT_PUBLIC_* environment variable. Use when introducing any new runtime env var.
Close out review findings — adjudicate each one, fix what deserves fixing, then reply on the PR threads or in the task's review file.
Review a change on three axes — spec compliance, repo standards, correctness — then publish the findings as inline PR comments or into a review file in the task folder.