[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CDZXY178EP82B8EYK1VCN4":3,"skill-same:01M7CDZXY178EP82B8EYK1VCN4":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7CDZXY178EP82B8EYK1VCN4","pipeliner-review-issue",null,"Review or resume the active Issue, remediate feedback before or after merge, and guide its exact candidate through the next PM gate.","Zuriel-Labs\u002Fpipeliner","Zuriel-Labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288671560?v=4","01M7CDYRRP6T1PMC5J81EW7THP","Zuriel Labs","01M7CDYRSB5S6R80KG66ENXD5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpipeliner-review-issue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pipeliner-review-issue\ndescription: Review or resume the active Issue, remediate feedback before or after merge, and guide its exact candidate through the next PM gate.\n---\n\n# Review an Issue\n\nApply the shared [installed repository home](..\u002Fpipeliner-maintain\u002Freferences\u002Fhome.md) and [message-only questions](..\u002Fpipeliner-maintain\u002Freferences\u002Fquestions.md) 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.\n\nFollow [Issue-based communication](..\u002F..\u002F..\u002FAGENTS.md#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.\n\nRead `AGENTS.md`, `pipeliner.config.json`, the sole active Issue, complete pull-request diff and history, acceptance criteria, specifications, candidate state, and applicable test guidance.\n\nThe 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\u002Fstatus readback.\n\n1. 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](..\u002Fpipeliner-work-issue\u002Freferences\u002Flifecycle.md). An open PR proceeds through review; a merged PR without findings resumes pending release verification\u002Facceptance instead of requiring another open PR. A merged PR with findings returns the same Issue to In Progress and uses a fresh remediation branch\u002FPR from the current owning phase branch, or default branch without a cycle.\n2. 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.\n3. 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\u002Fnative\u002Fimage builds stay local. Follow [local QA execution](..\u002Fpipeliner-work-issue\u002Freferences\u002Flocal-qa.md); agent review and preparation precede PM approval and do not require that approval as an entry condition.\n4. Remediate every finding on the current supporting branch (a fresh branch after merge). Repeat affected review and tests until no unresolved finding remains.\n5. For an open PR, confirm it is current, mergeable, and green for the exact committed head. Record source identity now; record artifact\u002Fenvironment identity when actually produced. Do not require future deployment identity at this stage.\n6. If a required review\u002Fnative candidate has not already been prepared and verified for this exact source, invoke `pipeliner-release-candidate`; otherwise reuse its verified evidence. For none\u002Fdirect-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.\n7. 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](..\u002Fpipeliner-maintain\u002Freferences\u002Frelease-cycle.md) 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\u002Fnative gates use their prepared artifact\u002Fenvironment. Do not ask for acceptance of an undeployed Production candidate.\n8. Present user-friendly numbered PM Testing steps following [the PM Testing contract](references\u002Fpm-testing.md), 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\u002Frelease\u002Fclose transition. PM feedback returns to the same feature branch\u002FPR for fixes and fresh verification. Questions use only clearly marked messages and wait indefinitely without timers.\n\nFor 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\u002Fintegration 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\u002Fdistribution or deployed identity before completion acceptance. Never require future final identity as a pre-deployment review gate. Production findings route to a governed development\u002Fstabilization branch on the same Issue, not a direct production fix.\n\nPM 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.\n","# Review an Issue\n\nApply the shared [installed repository home](..\u002Fpipeliner-maintain\u002Freferences\u002Fhome.md) and [message-only questions](..\u002Fpipeliner-maintain\u002Freferences\u002Fquestions.md) 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.\n\nFollow [Issue-based communication](..\u002F..\u002F..\u002FAGENTS.md#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.\n\nRead `AGENTS.md`, `pipeliner.config.json`, the sole active Issue, complete pull-request diff and history, acceptance criteria, specifications, candidate state, and applicable test guidance.\n\nThe 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\u002Fstatus readback.\n\n1. 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](..\u002Fpipeliner-work-issue\u002Freferences\u002Flifecycle.md). An open PR proceeds through review; a merged PR without findings resumes pending release verification\u002Facceptance instead of requiring another open PR. A merged PR with findings returns the same Issue to In Progress and uses a fresh remediation branch\u002FPR from the current owning phase branch, or default branch without a cycle.\n2. 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.\n3. 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\u002Fnative\u002Fimage builds stay local. Follow [local QA execution](..\u002Fpipeliner-work-issue\u002Freferences\u002Flocal-qa.md); agent review and preparation precede PM approval and do not require that approval as an entry condition.\n4. Remediate every finding on the current supporting branch (a fresh branch after merge). Repeat affected review and tests until no unresolved finding remains.\n5. For an open PR, confirm it is current, mergeable, and green for the exact committed head. Record source identity now; record artifact\u002Fenvironment identity when actually produced. Do not require future deployment identity at this stage.\n6. If a required review\u002Fnative candidate has not already been prepared and verified for this exact source, invoke `pipeliner-release-candidate`; otherwise reuse its verified evidence. For none\u002Fdirect-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.\n7. 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](..\u002Fpipeliner-maintain\u002Freferences\u002Frelease-cycle.md) 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\u002Fnative gates use their prepared artifact\u002Fenvironment. Do not ask for acceptance of an undeployed Production candidate.\n8. Present user-friendly numbered PM Testing steps following [the PM Testing contract](references\u002Fpm-testing.md), 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\u002Frelease\u002Fclose transition. PM feedback returns to the same feature branch\u002FPR for fixes and fresh verification. Questions use only clearly marked messages and wait indefinitely without timers.\n\nFor 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\u002Fintegration 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\u002Fdistribution or deployed identity before completion acceptance. Never require future final identity as a pre-deployment review gate. Production findings route to a governed development\u002Fstabilization branch on the same Issue, not a direct production fix.\n\nPM 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.\n",{"name":5,"description":7},"main","0af6febf92f8cca2ec3f78d5446d27cc4cfcf428",".agents\u002Fskills\u002Fpipeliner-review-issue","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner","https:\u002F\u002Fgithub.com\u002FZuriel-Labs","Our playground for apps, scripts, and code.","2026-11-12 05:17:16",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Zuriel-Labs\u002Fpipeliner --skill pipeliner-review-issue",{"tool":37,"command":38},"bunx","bunx skills add Zuriel-Labs\u002Fpipeliner --skill pipeliner-review-issue",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Zuriel-Labs\u002Fpipeliner --skill pipeliner-review-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpipeliner-review-issue\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",265,"https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpipeliner-review-issue\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fpm-testing.md",4717,"https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpipeliner-review-issue\u002Freferences\u002Fpm-testing.md",[56,63,70,76,83,90],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CE1MBMP52YARSJZ8N9ER7K","pipeliner-work-issue","Use the canonical workflow to start or resume one Issue and lead the next authorized stage.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-work-issue\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CE1CETB40RGJA8EM3R4ZGZ","pipeliner-update","Use the canonical workflow to update an existing Pipeliner adoption while preserving local configuration.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-update\u002FSKILL.md",[],[],{"skillNo":71,"name":5,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CE15VYS22AX9XGSGQCF61E","Use the canonical workflow to resume review or feedback before or after merge and guide PM Testing.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-review-issue\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CE0YV6EN1ZC6ESJ0TEK41V","pipeliner-release-production","Use the canonical workflow to release an approved candidate.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-release-production\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CE0P9YF5V416HMK6Z8YB6R","pipeliner-release-candidate","Use the canonical workflow to prepare an exact release candidate.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-release-candidate\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CE0MXSSR5STYA5P5VMT5VS","pipeliner-pipeline-health","Use the canonical workflow to audit pipeline health read-only.","https:\u002F\u002Fgithub.com\u002FZuriel-Labs\u002Fpipeliner\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpipeliner-pipeline-health\u002FSKILL.md",[],[]]