AGENT SKILL

pipeliner-review-issue

Review or resume the active Issue, remediate feedback before or after merge, and guide its exact candidate through the next PM gate.

License 许可
MIT
最近更新
2026-11-12
Stars
★ 0
Forks
0

01 前言 Front Matter

name
pipeliner-review-issue
description
Review or resume the active Issue, remediate feedback before or after merge, and guide its exact candidate through the next PM gate.

02 资源文件 2

03 SKILL.md 正文

Review an Issue

Apply the shared installed repository home and message-only questions contracts. First adoption retains its explicit-target gate. When an answer is needed, ask in the final ordinary message and end the turn immediately; no work or tool calls follow until the Human replies.

Follow Issue-based communication: identify the Issue first in findings, PM Testing handoffs, approval requests, and approval acknowledgments. Bind the configured approval to that Issue and exact candidate, retaining the pull request as review evidence.

Read AGENTS.md, pipeliner.config.json, the sole active Issue, complete pull-request diff and history, acceptance criteria, specifications, candidate state, and applicable test guidance.

The review candidate is the exact feature-branch PR presented in the Showcase. PM feedback and fixes stay on that Issue and candidate lane until the current pair re-verifies the changed candidate. Approval does not authorize a different Issue; after approval, only the exact approved PR may be merged and then the Issue may be closed after tree/status readback.

  1. Require the sole active Issue in In Progress or In Review and matching supporting PR evidence with the configured non-closing Issue reference. Follow lifecycle routing. An open PR proceeds through review; a merged PR without findings resumes pending release verification/acceptance instead of requiring another open PR. A merged PR with findings returns the same Issue to In Progress and uses a fresh remediation branch/PR from the current owning phase branch, or default branch without a cycle.
  2. Review correctness, regressions, security, privacy, authorization, data integrity, errors, concurrency, migrations, operations, accessibility, responsive UX, performance, compatibility, documentation, and tests in proportion to the change.
  3. Run focused tests, every configured quality command locally, diff checks, migration rehearsal, security checks, and hands-on application testing where applicable. Review all Actions transitive chains and CI review freshness; application/native/image builds stay local. Follow local QA execution; agent review and preparation precede PM approval and do not require that approval as an entry condition.
  4. Remediate every finding on the current supporting branch (a fresh branch after merge). Repeat affected review and tests until no unresolved finding remains.
  5. For an open PR, confirm it is current, mergeable, and green for the exact committed head. Record source identity now; record artifact/environment identity when actually produced. Do not require future deployment identity at this stage.
  6. If a required review/native candidate has not already been prepared and verified for this exact source, invoke pipeliner-release-candidate; otherwise reuse its verified evidence. For none/direct-production, prepare the local candidate directly. Evaluate circulating QA: finish the current pair on the latest candidate, then select the next stale pair. Present that pair's full Showcase and configured approval. Keep In Progress while a single-turn gate is pending; use exact native Pending Review for a circulating handoff, with assignment and status readback. After a PM reply, own cleanup, readback and continuation without another trigger.
  7. Move to In Review only after the applicable candidate and every configured QA turn are verified and cleanup is complete; immediately read back the card and active count. Follow the release-cycle contract when configured: development Issues use their integration gate; the Release Issue owns aggregate phase QA and all-PM acceptance. Otherwise follow the strategy's ordered gates. For simple none continue from the final required PM QA approval directly through exact-tree merge, verification, closure and cleanup; for direct-production request Production authorization against pre-release identity; immutable/native gates use their prepared artifact/environment. Do not ask for acceptance of an undeployed Production candidate.
  8. Present user-friendly numbered PM Testing steps following the PM Testing contract, limited to the actual next gate and the exact PR candidate. Put the exact configured phrase in its own fenced code block. On actual approval, revalidate identity and invoke pipeliner-close-issue for the next authorized merge/release/close transition. PM feedback returns to the same feature branch/PR for fixes and fresh verification. Questions use only clearly marked messages and wait indefinitely without timers.

For a cycle's final kind=production phase, select the actual configured delivery path. With a Production destination, distinguish pre-release Production authorization from final phase approval and verify deployment. With native-only multi-environment, prepare the Stable candidate and verify configured authorized native distribution/integration through the candidate and close skills, without calling pipeliner-release-production or inventing a service URL. Run aggregate latest-candidate QA and all-Human phase approvals against the actual final native/distribution or deployed identity before completion acceptance. Never require future final identity as a pre-deployment review gate. Production findings route to a governed development/stabilization branch on the same Issue, not a direct production fix.

PM findings are blocking. Move the Issue back to In Progress before remediation, create a new candidate, and repeat affected gates. Silence and earlier approval are not acceptance.

04 同仓库更多 Skills