[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B14PM4FV4A2NTWA6MY7FAD":3,"skill-same:01M7B14PM4FV4A2NTWA6MY7FAD":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7B14PM4FV4A2NTWA6MY7FAD","address-pr-review",null,"Seyal adapter for AI-SDLC review-stage remediation, adding GitHub PR, terminal architecture, repository-check, and human-ownership gates.","seyal-org\u002Fseyal","seyal-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329928416?v=4","01M7B14E8HB13K0XN49SA7N6ET","01M7B14E96WQ68374WDYVNMEZZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Faddress-pr-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: address-pr-review\ndescription: Seyal adapter for AI-SDLC review-stage remediation, adding GitHub PR, terminal architecture, repository-check, and human-ownership gates.\n---\n\n# Address PR review\n\nFollow the canonical generic procedure in `.sdlc\u002Fframework\u002Fskills\u002Fprocess-review\u002FSKILL.md`. If it is unavailable, run `make bootstrap-agents` first.\n\nAfter the approved one-batch remediation plan, use `python3 scripts\u002Fseyal-ai-sdlc-claim.py begin --repo seyal-org\u002Fseyal --phase process-review --number \u003CPR>`; require `verify` before every state\u002Fedit\u002Fpush\u002Fcomment write and `release` after the complete handoff. The wrapper uses the **same** PR lock as `pr-review`; `AI_SDLC_WORKER_ID` must be unique to each live worker. No lock is held while waiting for human approval.\n\nUse this for an existing Seyal PR whose candidate lifecycle stage is `IN_REVIEW` or `CLOSED_UNMERGED`. Reopen or rebase a closed unmerged head on that same pull request. Unfinished accepted-scope implementation remains under `implement-issue`. A decision blocker keeps this pull request and names the other one.\n\nApply only these Seyal-specific deltas:\n\n1. Map `merge_candidate_id` to the exact GitHub PR, current head SHA, owning Issue, deterministic human-owned branch, and modification authority. Read `candidate_lifecycle_stage` from `docs\u002Fengineering\u002FISSUE-PROTOCOL.md`: a draft PR is `IMPLEMENTATION_IN_PROGRESS`; a ready-for-review PR is `IN_REVIEW`; a closed unmerged PR that was not architecture-rejected is `CLOSED_UNMERGED`. Do not change the draft flag. Do not open a replacement PR.\n2. Fetch the **complete** unresolved review\u002Fcomment set plus all required failing checks. Never fix only the newest comment.\n3. Build one remediation ledger, group duplicate symptoms by root cause, and fix the complete known in-scope blocker set on the **same PR\u002Fbranch**. Never create a replacement implementation PR merely for remediation.\n4. Preserve Seyal architecture and hot-path invariants. A remediation that requires a new product\u002Farchitecture\u002Fsecurity authority decision stops and routes to that authority instead of being improvised in code.\n5. Re-run the narrow affected checks and then all invalidated repository\u002Fdomain evidence, including `make check` and any applicable conformance\u002Ffuzz\u002Fperformance\u002Fsecurity\u002Fnative\u002Fdocs gates.\n6. Re-fetch comments, checks and exact head before handoff. Known material findings must be resolved or explicitly blocked with evidence.\n7. Confirm that the full recorded root-cause set is addressed, re-fetch exact head\u002Freviews\u002FCI, then hand off the **same PR** for a full fresh `pr-review` (generic rule). Review is independent, not a self-approval. If the stage is `IMPLEMENTATION_IN_PROGRESS`, return to `implement-issue`. If `UNKNOWN`, stop and reconcile.\n\nHuman Issue ownership remains authoritative throughout remediation. Coding agents may assist but never become Seyal work owners or independent human reviewers.\n","# Address PR review\n\nFollow the canonical generic procedure in `.sdlc\u002Fframework\u002Fskills\u002Fprocess-review\u002FSKILL.md`. If it is unavailable, run `make bootstrap-agents` first.\n\nAfter the approved one-batch remediation plan, use `python3 scripts\u002Fseyal-ai-sdlc-claim.py begin --repo seyal-org\u002Fseyal --phase process-review --number \u003CPR>`; require `verify` before every state\u002Fedit\u002Fpush\u002Fcomment write and `release` after the complete handoff. The wrapper uses the **same** PR lock as `pr-review`; `AI_SDLC_WORKER_ID` must be unique to each live worker. No lock is held while waiting for human approval.\n\nUse this for an existing Seyal PR whose candidate lifecycle stage is `IN_REVIEW` or `CLOSED_UNMERGED`. Reopen or rebase a closed unmerged head on that same pull request. Unfinished accepted-scope implementation remains under `implement-issue`. A decision blocker keeps this pull request and names the other one.\n\nApply only these Seyal-specific deltas:\n\n1. Map `merge_candidate_id` to the exact GitHub PR, current head SHA, owning Issue, deterministic human-owned branch, and modification authority. Read `candidate_lifecycle_stage` from `docs\u002Fengineering\u002FISSUE-PROTOCOL.md`: a draft PR is `IMPLEMENTATION_IN_PROGRESS`; a ready-for-review PR is `IN_REVIEW`; a closed unmerged PR that was not architecture-rejected is `CLOSED_UNMERGED`. Do not change the draft flag. Do not open a replacement PR.\n2. Fetch the **complete** unresolved review\u002Fcomment set plus all required failing checks. Never fix only the newest comment.\n3. Build one remediation ledger, group duplicate symptoms by root cause, and fix the complete known in-scope blocker set on the **same PR\u002Fbranch**. Never create a replacement implementation PR merely for remediation.\n4. Preserve Seyal architecture and hot-path invariants. A remediation that requires a new product\u002Farchitecture\u002Fsecurity authority decision stops and routes to that authority instead of being improvised in code.\n5. Re-run the narrow affected checks and then all invalidated repository\u002Fdomain evidence, including `make check` and any applicable conformance\u002Ffuzz\u002Fperformance\u002Fsecurity\u002Fnative\u002Fdocs gates.\n6. Re-fetch comments, checks and exact head before handoff. Known material findings must be resolved or explicitly blocked with evidence.\n7. Confirm that the full recorded root-cause set is addressed, re-fetch exact head\u002Freviews\u002FCI, then hand off the **same PR** for a full fresh `pr-review` (generic rule). Review is independent, not a self-approval. If the stage is `IMPLEMENTATION_IN_PROGRESS`, return to `implement-issue`. If `UNKNOWN`, stop and reconcile.\n\nHuman Issue ownership remains authoritative throughout remediation. Coding agents may assist but never become Seyal work owners or independent human reviewers.\n",{"name":5,"description":7},"master","805201cf9d73f4c0e048eb6b35b5539a4e3b6531",".agents\u002Fskills\u002Faddress-pr-review",1,"https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal","https:\u002F\u002Fgithub.com\u002Fseyal-org","2026-11-14 23:45:58",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add seyal-org\u002Fseyal --skill address-pr-review",{"tool":36,"command":37},"bunx","bunx skills add seyal-org\u002Fseyal --skill address-pr-review",{"tool":39,"command":40},"pnpm","pnpm dlx skills add seyal-org\u002Fseyal --skill address-pr-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Faddress-pr-review\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7B17NTBFBQVEH5925KR3Q38","vt-tdd","Claude adapter for Seyal VT test-driven development.","https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fvt-tdd\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7B17MR7XT2A0354TAVWECS8","visual-regression","Claude adapter for Seyal visual regression review.","https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fvisual-regression\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7B17JCHAFCE7R8WMMSJW1B0","verification","Claude adapter for Seyal outcome verification.","https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7B17H9CJHTK8RWNET4PBDP6","terminal-conformance","Claude adapter for Seyal terminal conformance validation.","https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fterminal-conformance\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7B17EX5TH6EJKPY7STEK496","security-review","Claude adapter for Seyal threat-oriented security review.","https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7B17DY0G830HH6M0HKZY69E","rust-fuzzing","Claude adapter for Seyal Rust fuzzing.","https:\u002F\u002Fgithub.com\u002Fseyal-org\u002Fseyal\u002Fblob\u002Fmaster\u002F.claude\u002Fskills\u002Frust-fuzzing\u002FSKILL.md",[],[]]