issue-close-evidence-flow

스타11

포크1

업데이트2026년 4월 29일 06:20

Prepare compliant closure evidence comments for normal Issues and milestone management Issues. Use when Codex is about to close an Issue and needs the exact closure evidence body, including code versus non-code handling, follow-up links, and milestone audit-log rows when required.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

tts1374

tts1374/infinitas_arena

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Issue Close Evidence Flow

Overview

Use this skill only when the work is actually ready to close or when you need to identify what evidence is still missing. Do not use it for generic progress reports. Return a close-ready evidence artifact or a concrete missing-evidence block, not a best-effort summary.

Inputs

Issue type:
- normal Issue
- milestone management Issue
Completion mode:
- code
- non-code
PR URL or commit SHA, if code
Follow-up Issue/PR links, if any
Follow-up detection sources:
- Issue body / comments
- merged PR body / comments
- Phase D output
- tasks/issue-*.md

Workflow

Decide whether the closure is code or non-code.
Collect closure evidence:
- PR URL or commit SHA when code
- non-code completion reason when non-code
Detect follow-ups only from explicit sources:
- Issue body / comments
- merged PR body / comments
- Phase D output
- tasks/issue-*.md
If follow-up is only inferable and not explicitly linked, stop with BLOCKED.
Load docs/issue_close_evidence_template.md.
Fill the closure-evidence section.
If the Issue is a milestone-management Issue, add the milestone audit table too.
If executing the close, prefer the structured connector/write path when available.
Empty stdout / empty CLI response / confirmation absent response is not success evidence. If the first write path fails or cannot confirm creation, switch method and require exact read-back.
Confirm the closure evidence comment exists by returned comment URL/id or exact-body read-back before closing the Issue.
Use references/closure-checklist.md to verify status vocabulary, links, follow-up evidence completeness, and close ordering.

Do not:

replace the caller's readiness judgment with invented closure assumptions
infer follow-up ownership or completion from implication alone

Output Contract

Always return:

Close recommendation
Missing evidence
Comment body
Final status

Rules:

If required evidence is missing, recommend BLOCKED instead of fabricating closure text.
Preserve repository status vocabulary.
For non-code closure, explain why code evidence is N/A.
If no explicit follow-up is found, write なし.
Do not invent follow-up numbers from implication alone.
Closure evidence comment must be ready before recommending the close action.
Empty or silent write-back responses are not closure evidence.
Do not close an Issue until the posted closure evidence comment is confirmed to exist.

이 저장소의 다른 Skills

같은 저장소

commit-pr-flow

tts1374/infinitas_arena

Run a Phase C commit and PR flow from bounded plan items with strict scope control, validation gating, and review-ready output. Use when implementation is done and you need to stage intended files only, verify plan-to-diff alignment, create logical commits, and prepare or open a PR.

2026-05-0911

phase-c-kickoff-flow

tts1374/infinitas_arena

Create Phase C kickoff artifacts before implementation starts. Use when Phase A/B is already decided and Codex needs to restate the source of truth, re-judge execution profile, apply the Spawn Gate, and emit a `delegation execution record` from an Issue, `tasks/*.md`, or, only when concrete task artifacts are not required, an A-lite agreement.

2026-05-0911

phase-c-review-response-flow

tts1374/infinitas_arena

Handle a PR review iteration as a bounded Phase C continuation. Use when Codex receives review URLs or threads and needs to inspect actionable comments, keep scope anchored to the original Issue/task, rerun required validation/audit, and prepare or execute reply/resolve/re-review steps.

2026-05-0911

plan-mode-gate

tts1374/infinitas_arena

Reference skill for execution-profile and Plan Mode decision support. Used by strategy_orchestrator or execution_coordinator to classify `Local-Fast / Standard / High-Risk`, determine whether Plan Mode is required, and emit a Spawn Gate hint before implementation. This skill does not replace stage/routing decisions and does not by itself authorize implementation.

2026-05-0911

quality-check-matrix

tts1374/infinitas_arena

Reference skill for validation-scope selection. Used by orchestrators, implementers, or auditors to map touched areas to the minimum required verification groups from QUALITY.md. This skill does not replace audit/completion decisions and does not by itself declare a task complete.

2026-05-0911

branch-latest-sync-flow

tts1374/infinitas_arena

Safely sync a base/default branch such as `v1` to the latest upstream state while classifying dirty paths, preserving real user WIP, and reconciling upstream-equivalent residue.

2026-04-2911

name	issue-close-evidence-flow
description	Prepare compliant closure evidence comments for normal Issues and milestone management Issues. Use when Codex is about to close an Issue and needs the exact closure evidence body, including code versus non-code handling, follow-up links, and milestone audit-log rows when required.

Issue Close Evidence Flow

Overview

Inputs

Issue type:
- normal Issue
- milestone management Issue
Completion mode:
- code
- non-code
PR URL or commit SHA, if code
Follow-up Issue/PR links, if any
Follow-up detection sources:
- Issue body / comments
- merged PR body / comments
- Phase D output
- tasks/issue-*.md

Workflow

Decide whether the closure is code or non-code.
Collect closure evidence:
- PR URL or commit SHA when code
- non-code completion reason when non-code
Detect follow-ups only from explicit sources:
- Issue body / comments
- merged PR body / comments
- Phase D output
- tasks/issue-*.md
If follow-up is only inferable and not explicitly linked, stop with BLOCKED.
Load docs/issue_close_evidence_template.md.
Fill the closure-evidence section.
If the Issue is a milestone-management Issue, add the milestone audit table too.
If executing the close, prefer the structured connector/write path when available.
Empty stdout / empty CLI response / confirmation absent response is not success evidence. If the first write path fails or cannot confirm creation, switch method and require exact read-back.
Confirm the closure evidence comment exists by returned comment URL/id or exact-body read-back before closing the Issue.
Use references/closure-checklist.md to verify status vocabulary, links, follow-up evidence completeness, and close ordering.

Do not:

replace the caller's readiness judgment with invented closure assumptions
infer follow-up ownership or completion from implication alone

Output Contract

Always return:

Close recommendation
Missing evidence
Comment body
Final status

Rules:

If required evidence is missing, recommend BLOCKED instead of fabricating closure text.
Preserve repository status vocabulary.
For non-code closure, explain why code evidence is N/A.
If no explicit follow-up is found, write なし.
Do not invent follow-up numbers from implication alone.
Closure evidence comment must be ready before recommending the close action.
Empty or silent write-back responses are not closure evidence.
Do not close an Issue until the posted closure evidence comment is confirmed to exist.