[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ENFTPP93ZDTWJRE69CMSYT":3,"skill-same:01M7ENFTPP93ZDTWJRE69CMSYT":56},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ENFTPP93ZDTWJRE69CMSYT","loopx-pr-program",null,"Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more repositories: inventory current change requests, reconcile new\u002Fmerged\u002Fclosed or retargeted work, preserve requirement and dependency priorities, maintain a roadmap document, or monitor material lifecycle\u002Fcheck\u002Freview changes over time. Use provider-neutral snapshots and one grouped continuous monitor; do not use for deep per-PR code review, approval, commenting, or merge actions.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Floopx-pr-program\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: loopx-pr-program\ndescription: \"Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more repositories: inventory current change requests, reconcile new\u002Fmerged\u002Fclosed or retargeted work, preserve requirement and dependency priorities, maintain a roadmap document, or monitor material lifecycle\u002Fcheck\u002Freview changes over time. Use provider-neutral snapshots and one grouped continuous monitor; do not use for deep per-PR code review, approval, commenting, or merge actions.\"\n---\n\n# LoopX PR Program\n\nManage a delivery program as durable LoopX state instead of rebuilding a queue\nfrom chat memory. Keep source acquisition provider-local, normalize observations\ninto one public contract, and write back only material transitions.\n\n## Route The Request\n\nUse this workflow when the user asks to manage, prioritize, reconcile, document,\nor monitor several pull requests or merge requests. Route a deep review of each\nselected PR to `loopx-pr-review`. Route approval, comments, reruns, branch\nretargeting, closing, or merging to the normal provider-specific workflow and\nrequire the corresponding authority.\n\nTreat document maintenance and monitor creation as writes. A request to update\nthe roadmap or keep monitoring the program authorizes those scoped writes; an\nordinary status question remains read-only.\n\n## Start From LoopX State\n\nStart or join the project goal before material work. Represent the program with\none advancement todo for the current reconciliation and one\n`continuous_monitor` todo for recurring observation. Do not create one monitor\ntodo per change request.\n\nUse a stable monitor identity:\n\n```text\ntask_class=continuous_monitor\naction_kind=pr_program_reconcile\ntarget_key=pr-program-\u003Cstable-program-id>\ncadence=\u003Cuser cadence or 30m>\n```\n\nPreserve `claimed_by`, `last_checked_at`, `next_due_at`, `result_hash`,\n`consecutive_no_change`, and `material_change`. Quiet monitor polls keep\nliveness but do not count as delivery progress, rewrite roadmap documents, or\nspend progress quota.\n\n## Acquire A Complete Snapshot\n\nUse any authorized source-control read interface available in the current\nenvironment. Prefer one batch query for inventory and targeted reads for the\nitems that changed. Never encode a private transport command, executable name,\ncredential, internal hostname, or document token in this skill, repository\nexamples, committed fixtures, or public evidence.\n\nNormalize observations using\n[`references\u002Fsnapshot-contract.md`](references\u002Fsnapshot-contract.md). Mark\n`result_completeness.complete=true` only after proving the requested repository,\nauthor, state, and time-window inventory is exhaustive. An incomplete current\nsnapshot must not make absent rows look closed or removed.\nPersist the structured scope fingerprint with the baseline. Do not advance the\ndurable baseline or grouped-monitor `result_hash` from an incomplete snapshot\nor when the previous and current scope fingerprints differ; otherwise a partial\npage or narrowed query can create false remove\u002Fre-add transitions on the next\npoll.\n\nStore raw and normalized snapshots under an ignored owner-local directory such\nas `.local\u002Floopx\u002Fpr-program\u002F\u003Cprogram-id>\u002F`. Verify the path with\n`git check-ignore` before writing. If no ignored path is available, use a\ntemporary directory and keep only a redacted evidence summary in LoopX state.\n\n## Reconcile Material Changes\n\nRun the bundled delta helper before manually comparing rows:\n\n```bash\npython skills\u002Floopx-pr-program\u002Fscripts\u002Fdiff_snapshot.py \\\n  --previous \u003Cprevious.json> \\\n  --current \u003Ccurrent.json> \\\n  --output \u003Cdelta.json>\n```\n\nOmit `--previous` for the first baseline. The helper treats lifecycle, draft,\ntarget branch, head revision, checks, review, work item, requirement, theme,\npriority, and dependency changes as material. Timestamp-only movement is\nobservation noise. Read the actual description, latest review context, checks,\nand changed-file evidence for every added or materially changed row before\nupdating the program judgment.\n\nDo not infer motivation or priority from title, number, author, age, or green CI\nalone. Product requirements set priority. Correctness dependencies and real\nmerge gates determine order within a priority. Record a requirement gap\nexplicitly when no change request implements part of the requested behavior;\ndo not call the requirement complete because a neighboring parameter or feature\nlanded.\n\n## Compose With An Integration Branch\n\nWhen several selected change requests belong to one repository, compose this\nprogram view with LoopX's `integration-branch-reconcile` capability. Keep the\nownership split explicit:\n\n- this skill decides which changes belong in the candidate and why;\n- the integration-branch plan records their ordered local source refs and\n  proves what exact code is composed.\n\nDo not populate the plan from every open or P0 change request automatically.\nSelect sources from explicit program scope, dependency order, and current\nreview intent. Refresh the local refs through the authorized host workflow,\nthen verify that each selected ref resolves to the observed `head_sha` before\nconfiguring or syncing the integration branch. A mismatch is source evidence\ndrift, not permission to merge a stale local ref.\n\nUse the same grouped program monitor to read both the normalized change-request\ndelta and `loopx integration-branch status --format json`. Treat base\u002Fsource\nmovement, an unexpected integration head, and merge conflict as material\nprogram evidence. A monitor poll remains read-only: it may report that the\ncandidate needs reconciliation, but it must not run `sync --execute` by itself.\nThat command is a separate, explicit local write and never grants authority to\npush, retarget, approve, or merge a remote change request.\n\n## Project The Program\n\nKeep one canonical program projection with three sections:\n\n1. completed work, grouped by product theme;\n2. pending work, grouped by product theme, with archived or superseded\n   development stacks nested under the surviving change request;\n3. merge priority, ordered first by explicit product priority, then dependency,\n   correctness risk, and current merge gate.\n\nKeep links at the end of each compact row. Preserve the target document's\nexisting heading, color, callout, and strike-through conventions. Update only\nthe affected blocks, refetch them after writing, and verify that unrelated\ncontent and resource blocks remain unchanged.\n\nFor every priority row, distinguish these facts:\n\n- shipped behavior and requirement coverage;\n- dependency or recommended merge order;\n- current checks, review, and external work-item gates;\n- missing implementation or validation that no existing change request covers.\n\n## Write Back And Continue\n\nAfter a validated material change:\n\n1. update the grouped monitor `result_hash` and reset\n   `consecutive_no_change=0`;\n2. update the roadmap and refetch the changed sections;\n3. complete the reconciliation todo with compact evidence and create a\n   successor only when concrete follow-up remains;\n4. refresh LoopX state with the actual delivery classification and outcome;\n5. spend quota only after the state and document writeback are validated.\n\nAfter a quiet poll, update monitor scheduling metadata and increment\n`consecutive_no_change`; do not produce a synthetic progress event.\n\n## Public And Private Boundary\n\nCommit only the provider-neutral contract, algorithm, and redacted fixtures.\nKeep private provider adapters, source commands, raw comments, internal URLs,\ndocument ids, snapshots, and organization-specific prioritization outside the\npublic repository. Before staging changes to this skill or its resources, scan\nthe exact paths for private hostnames, executable names, credentials, local\nabsolute paths, and raw operating context.\n","# LoopX PR Program\n\nManage a delivery program as durable LoopX state instead of rebuilding a queue\nfrom chat memory. Keep source acquisition provider-local, normalize observations\ninto one public contract, and write back only material transitions.\n\n## Route The Request\n\nUse this workflow when the user asks to manage, prioritize, reconcile, document,\nor monitor several pull requests or merge requests. Route a deep review of each\nselected PR to `loopx-pr-review`. Route approval, comments, reruns, branch\nretargeting, closing, or merging to the normal provider-specific workflow and\nrequire the corresponding authority.\n\nTreat document maintenance and monitor creation as writes. A request to update\nthe roadmap or keep monitoring the program authorizes those scoped writes; an\nordinary status question remains read-only.\n\n## Start From LoopX State\n\nStart or join the project goal before material work. Represent the program with\none advancement todo for the current reconciliation and one\n`continuous_monitor` todo for recurring observation. Do not create one monitor\ntodo per change request.\n\nUse a stable monitor identity:\n\n```text\ntask_class=continuous_monitor\naction_kind=pr_program_reconcile\ntarget_key=pr-program-\u003Cstable-program-id>\ncadence=\u003Cuser cadence or 30m>\n```\n\nPreserve `claimed_by`, `last_checked_at`, `next_due_at`, `result_hash`,\n`consecutive_no_change`, and `material_change`. Quiet monitor polls keep\nliveness but do not count as delivery progress, rewrite roadmap documents, or\nspend progress quota.\n\n## Acquire A Complete Snapshot\n\nUse any authorized source-control read interface available in the current\nenvironment. Prefer one batch query for inventory and targeted reads for the\nitems that changed. Never encode a private transport command, executable name,\ncredential, internal hostname, or document token in this skill, repository\nexamples, committed fixtures, or public evidence.\n\nNormalize observations using\n[`references\u002Fsnapshot-contract.md`](references\u002Fsnapshot-contract.md). Mark\n`result_completeness.complete=true` only after proving the requested repository,\nauthor, state, and time-window inventory is exhaustive. An incomplete current\nsnapshot must not make absent rows look closed or removed.\nPersist the structured scope fingerprint with the baseline. Do not advance the\ndurable baseline or grouped-monitor `result_hash` from an incomplete snapshot\nor when the previous and current scope fingerprints differ; otherwise a partial\npage or narrowed query can create false remove\u002Fre-add transitions on the next\npoll.\n\nStore raw and normalized snapshots under an ignored owner-local directory such\nas `.local\u002Floopx\u002Fpr-program\u002F\u003Cprogram-id>\u002F`. Verify the path with\n`git check-ignore` before writing. If no ignored path is available, use a\ntemporary directory and keep only a redacted evidence summary in LoopX state.\n\n## Reconcile Material Changes\n\nRun the bundled delta helper before manually comparing rows:\n\n```bash\npython skills\u002Floopx-pr-program\u002Fscripts\u002Fdiff_snapshot.py \\\n  --previous \u003Cprevious.json> \\\n  --current \u003Ccurrent.json> \\\n  --output \u003Cdelta.json>\n```\n\nOmit `--previous` for the first baseline. The helper treats lifecycle, draft,\ntarget branch, head revision, checks, review, work item, requirement, theme,\npriority, and dependency changes as material. Timestamp-only movement is\nobservation noise. Read the actual description, latest review context, checks,\nand changed-file evidence for every added or materially changed row before\nupdating the program judgment.\n\nDo not infer motivation or priority from title, number, author, age, or green CI\nalone. Product requirements set priority. Correctness dependencies and real\nmerge gates determine order within a priority. Record a requirement gap\nexplicitly when no change request implements part of the requested behavior;\ndo not call the requirement complete because a neighboring parameter or feature\nlanded.\n\n## Compose With An Integration Branch\n\nWhen several selected change requests belong to one repository, compose this\nprogram view with LoopX's `integration-branch-reconcile` capability. Keep the\nownership split explicit:\n\n- this skill decides which changes belong in the candidate and why;\n- the integration-branch plan records their ordered local source refs and\n  proves what exact code is composed.\n\nDo not populate the plan from every open or P0 change request automatically.\nSelect sources from explicit program scope, dependency order, and current\nreview intent. Refresh the local refs through the authorized host workflow,\nthen verify that each selected ref resolves to the observed `head_sha` before\nconfiguring or syncing the integration branch. A mismatch is source evidence\ndrift, not permission to merge a stale local ref.\n\nUse the same grouped program monitor to read both the normalized change-request\ndelta and `loopx integration-branch status --format json`. Treat base\u002Fsource\nmovement, an unexpected integration head, and merge conflict as material\nprogram evidence. A monitor poll remains read-only: it may report that the\ncandidate needs reconciliation, but it must not run `sync --execute` by itself.\nThat command is a separate, explicit local write and never grants authority to\npush, retarget, approve, or merge a remote change request.\n\n## Project The Program\n\nKeep one canonical program projection with three sections:\n\n1. completed work, grouped by product theme;\n2. pending work, grouped by product theme, with archived or superseded\n   development stacks nested under the surviving change request;\n3. merge priority, ordered first by explicit product priority, then dependency,\n   correctness risk, and current merge gate.\n\nKeep links at the end of each compact row. Preserve the target document's\nexisting heading, color, callout, and strike-through conventions. Update only\nthe affected blocks, refetch them after writing, and verify that unrelated\ncontent and resource blocks remain unchanged.\n\nFor every priority row, distinguish these facts:\n\n- shipped behavior and requirement coverage;\n- dependency or recommended merge order;\n- current checks, review, and external work-item gates;\n- missing implementation or validation that no existing change request covers.\n\n## Write Back And Continue\n\nAfter a validated material change:\n\n1. update the grouped monitor `result_hash` and reset\n   `consecutive_no_change=0`;\n2. update the roadmap and refetch the changed sections;\n3. complete the reconciliation todo with compact evidence and create a\n   successor only when concrete follow-up remains;\n4. refresh LoopX state with the actual delivery classification and outcome;\n5. spend quota only after the state and document writeback are validated.\n\nAfter a quiet poll, update monitor scheduling metadata and increment\n`consecutive_no_change`; do not produce a synthetic progress event.\n\n## Public And Private Boundary\n\nCommit only the provider-neutral contract, algorithm, and redacted fixtures.\nKeep private provider adapters, source commands, raw comments, internal URLs,\ndocument ids, snapshots, and organization-specific prioritization outside the\npublic repository. Before staging changes to this skill or its resources, scan\nthe exact paths for private hostnames, executable names, credentials, local\nabsolute paths, and raw operating context.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Floopx-pr-program",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill loopx-pr-program",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill loopx-pr-program",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill loopx-pr-program","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Floopx-pr-program\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",301,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Floopx-pr-program\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fsnapshot-contract.md",4892,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Floopx-pr-program\u002Freferences\u002Fsnapshot-contract.md",[57,65,70,77,84,91],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":64},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":66,"name":59,"nameZh":6,"description":60,"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":64},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":64},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":64},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":64},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":64},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]