[Nikola Metulev (nmetulev)]

Description

Make lifecycle labels describe whether the agent has finished its work, rather than whether a reviewer has responded:

• Reserve agent-blocked for feedback or CI the agent cannot finish without help, or missing author input.
• Use ready-for-review when agent work and technical checks are complete, including while awaiting re-review of addressed feedback.
• Use labels instead of automated lifecycle/status comments. Keep operational details in session checkpoints; necessary review-feedback replies remain required.
• Keep pending approvals distinct without dismissing a human changes-request review or implying permission to merge.
• Continue configured follow-through while requested re-review is pending.

The initial independent assessment and ordinary validation/CI waits remain preparation work.

Usage Example

Illustrative workflow decisions:

Situation	Lifecycle label
Feedback addressed and checks green; reviewer has not reassessed yet	ready-for-review
Agent is fixing a finding or waiting for required CI	agent-preparing
Agent cannot address feedback/fix CI with available access, or needs an author decision	agent-blocked

ready-for-review does not override GitHub's approval or merge requirements. Status belongs in the label, not a recurring PR progress comment.

Related Issue

N/A — requested contributor-workflow policy clarification.

Type of Change

• 📝 Documentation

Checklist

• Validated the contributor skill's frontmatter, relative links, Markdown fences, and label references locally on Windows.
• git diff --check passes.

Screenshots / Demo

N/A — contributor instructions only; no application or CLI runtime changes.

Additional Notes

The repository label was already renamed from agent-ready-for-review to ready-for-review with explicit authorization; existing memberships were preserved. Its descriptions and the active agents' instructions were updated to match.

No full NativeAOT build was run for this contributor Markdown-only change.

AI Description

This section is auto-generated by AI when the PR is opened or updated. To opt out, delete this entire section including the marker comments.

[Copilot]

Copilot review overview

🟢 Approval recommended

The documentation is internally consistent and has no unresolved issues.

Review effort: Balanced
Findings: None

What changed in this PR

Clarifies PR lifecycle labels so they reflect agent progress independently of pending human approval.

Changes:

• Defines when to use agent-preparing, agent-blocked, and ready-for-review.
• Keeps re-review status visible while continuing configured follow-through.

File	Description
.github/​skills/​pr-lifecycle/​SKILL.md	Updates lifecycle and re-review guidance.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.