[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXGAYP817KY5JS2HW8ZRAZ":3,"skill-same:01M7EXGAYP817KY5JS2HW8ZRAZ":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7EXGAYP817KY5JS2HW8ZRAZ","bug-report",null,"Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.","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\u002F05-技能与代理开发\u002Fbug-report\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bug-report\ndescription: \"Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.\"\nargument-hint: \"[description] | analyze [path-to-file]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep, Write\n---\n\n## Phase 1: Parse Arguments\n\nDetermine the mode from the argument:\n\n- No keyword → **Description Mode**: generate a structured bug report from the provided description\n- `analyze [path]` → **Analyze Mode**: read the target file(s) and identify potential bugs\n- `verify [BUG-ID]` → **Verify Mode**: confirm a reported fix actually resolved the bug\n- `close [BUG-ID]` → **Close Mode**: mark a verified bug as closed with resolution record\n\nIf no argument is provided, ask the user for a bug description before proceeding.\n\n---\n\n## Phase 2A: Description Mode\n\n1. **Parse the description** for key information: what broke, when, how to reproduce it, and what the expected behavior is.\n\n2. **Search the codebase** for related files using Grep\u002FGlob to add context (affected system, likely files).\n\n3. **Draft the bug report**:\n\n```markdown\n# Bug Report\n\n## Summary\n**Title**: [Concise, descriptive title]\n**ID**: BUG-[NNNN]\n**Severity**: [S1-Critical \u002F S2-Major \u002F S3-Minor \u002F S4-Trivial]\n**Priority**: [P1-Immediate \u002F P2-Next Sprint \u002F P3-Backlog \u002F P4-Wishlist]\n**Status**: Open\n**Reported**: [Date]\n**Reporter**: [Name]\n\n## Classification\n- **Category**: [Gameplay \u002F UI \u002F Audio \u002F Visual \u002F Performance \u002F Crash \u002F Network]\n- **System**: [Which game system is affected]\n- **Frequency**: [Always \u002F Often (>50%) \u002F Sometimes (10-50%) \u002F Rare (\u003C10%)]\n- **Regression**: [Yes\u002FNo\u002FUnknown -- was this working before?]\n\n## Environment\n- **Build**: [Version or commit hash]\n- **Platform**: [OS, hardware if relevant]\n- **Scene\u002FLevel**: [Where in the game]\n- **Game State**: [Relevant state -- inventory, quest progress, etc.]\n\n## Reproduction Steps\n**Preconditions**: [Required state before starting]\n\n1. [Exact step 1]\n2. [Exact step 2]\n3. [Exact step 3]\n\n**Expected Result**: [What should happen]\n**Actual Result**: [What actually happens]\n\n## Technical Context\n- **Likely affected files**: [List of files based on codebase search]\n- **Related systems**: [What other systems might be involved]\n- **Possible root cause**: [If identifiable from the description]\n\n## Evidence\n- **Logs**: [Relevant log output if available]\n- **Visual**: [Description of visual evidence]\n\n## Related Issues\n- [Links to related bugs or design documents]\n\n## Notes\n[Any additional context or observations]\n```\n\n---\n\n## Phase 2B: Analyze Mode\n\n1. **Read the target file(s)** specified in the argument.\n\n2. **Identify potential bugs**: null references, off-by-one errors, race conditions, unhandled edge cases, resource leaks, incorrect state transitions.\n\n3. **For each potential bug**, generate a bug report using the template above, with the likely trigger scenario and recommended fix filled in.\n\n---\n\n## Phase 2C: Verify Mode\n\nRead `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md`. Extract the reproduction steps and expected result.\n\n1. **Re-run reproduction steps** — use Grep\u002FGlob to check whether the root cause code path still exists as described. If the fix removed or changed it, note the change.\n2. **Run the related test** — if the bug's system has a test file in `tests\u002F`, run it via Bash and report pass\u002Ffail.\n3. **Check for regression** — grep the codebase for any new occurrence of the pattern that caused the bug.\n\nProduce a verification verdict:\n\n- **VERIFIED FIXED** — reproduction steps no longer produce the bug; related tests pass\n- **STILL PRESENT** — bug reproduces as described; fix did not resolve the issue\n- **CANNOT VERIFY** — automated checks inconclusive; manual playtest required\n\nAsk: \"May I update `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md` to set Status: Verified Fixed \u002F Still Present \u002F Cannot Verify?\"\n\nIf STILL PRESENT: reopen the bug, set Status back to Open, and suggest re-running `\u002Fhotfix [BUG-ID]`.\n\n---\n\n## Phase 2D: Close Mode\n\nRead `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md`. Confirm Status is `Verified Fixed` before closing. If status is anything else, stop: \"Bug [ID] must be Verified Fixed before it can be closed. Run `\u002Fbug-report verify [BUG-ID]` first.\"\n\nAppend a closure record to the bug file:\n\n```markdown\n## Closure Record\n**Closed**: [date]\n**Resolution**: Fixed — [one-line description of what was changed]\n**Fix commit \u002F PR**: [if known]\n**Verified by**: qa-tester\n**Closed by**: [user]\n**Regression test**: [test file path, or \"Manual verification\"]\n**Status**: Closed\n```\n\nUpdate the top-level `**Status**: Open` field to `**Status**: Closed`.\n\nAsk: \"May I update `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md` to mark it Closed?\"\n\nAfter closing, check `production\u002Fqa\u002Fbug-triage-*.md` — if the bug appears in an open triage report, note: \"Bug [ID] is referenced in the triage report. Run `\u002Fbug-triage` to refresh the open bug count.\"\n\n---\n\n## Phase 3: Save Report\n\nPresent the completed bug report(s) to the user.\n\nAsk: \"May I write this to `production\u002Fqa\u002Fbugs\u002FBUG-[NNNN].md`?\"\n\nIf yes, write the file, creating the directory if needed. Verdict: **COMPLETE** — bug report filed.\n\nIf no, stop here. Verdict: **BLOCKED** — user declined write.\n\n---\n\n## Phase 4: Next Steps\n\nAfter saving, suggest based on mode:\n\n**After filing (Description\u002FAnalyze mode):**\n- Run `\u002Fbug-triage` to prioritize alongside existing open bugs\n- If S1 or S2: run `\u002Fhotfix [BUG-ID]` for emergency fix workflow\n\n**After fixing the bug (developer confirms fix is in):**\n- Run `\u002Fbug-report verify [BUG-ID]` — confirm the fix actually works before closing\n- Never mark a bug closed without verification — a fix that doesn't verify is still Open\n\n**After verify returns VERIFIED FIXED:**\n- Run `\u002Fbug-report close [BUG-ID]` — write the closure record and update status\n- Run `\u002Fbug-triage` to refresh the open bug count and remove it from the active list\n","## Phase 1: Parse Arguments\n\nDetermine the mode from the argument:\n\n- No keyword → **Description Mode**: generate a structured bug report from the provided description\n- `analyze [path]` → **Analyze Mode**: read the target file(s) and identify potential bugs\n- `verify [BUG-ID]` → **Verify Mode**: confirm a reported fix actually resolved the bug\n- `close [BUG-ID]` → **Close Mode**: mark a verified bug as closed with resolution record\n\nIf no argument is provided, ask the user for a bug description before proceeding.\n\n---\n\n## Phase 2A: Description Mode\n\n1. **Parse the description** for key information: what broke, when, how to reproduce it, and what the expected behavior is.\n\n2. **Search the codebase** for related files using Grep\u002FGlob to add context (affected system, likely files).\n\n3. **Draft the bug report**:\n\n```markdown\n# Bug Report\n\n## Summary\n**Title**: [Concise, descriptive title]\n**ID**: BUG-[NNNN]\n**Severity**: [S1-Critical \u002F S2-Major \u002F S3-Minor \u002F S4-Trivial]\n**Priority**: [P1-Immediate \u002F P2-Next Sprint \u002F P3-Backlog \u002F P4-Wishlist]\n**Status**: Open\n**Reported**: [Date]\n**Reporter**: [Name]\n\n## Classification\n- **Category**: [Gameplay \u002F UI \u002F Audio \u002F Visual \u002F Performance \u002F Crash \u002F Network]\n- **System**: [Which game system is affected]\n- **Frequency**: [Always \u002F Often (>50%) \u002F Sometimes (10-50%) \u002F Rare (\u003C10%)]\n- **Regression**: [Yes\u002FNo\u002FUnknown -- was this working before?]\n\n## Environment\n- **Build**: [Version or commit hash]\n- **Platform**: [OS, hardware if relevant]\n- **Scene\u002FLevel**: [Where in the game]\n- **Game State**: [Relevant state -- inventory, quest progress, etc.]\n\n## Reproduction Steps\n**Preconditions**: [Required state before starting]\n\n1. [Exact step 1]\n2. [Exact step 2]\n3. [Exact step 3]\n\n**Expected Result**: [What should happen]\n**Actual Result**: [What actually happens]\n\n## Technical Context\n- **Likely affected files**: [List of files based on codebase search]\n- **Related systems**: [What other systems might be involved]\n- **Possible root cause**: [If identifiable from the description]\n\n## Evidence\n- **Logs**: [Relevant log output if available]\n- **Visual**: [Description of visual evidence]\n\n## Related Issues\n- [Links to related bugs or design documents]\n\n## Notes\n[Any additional context or observations]\n```\n\n---\n\n## Phase 2B: Analyze Mode\n\n1. **Read the target file(s)** specified in the argument.\n\n2. **Identify potential bugs**: null references, off-by-one errors, race conditions, unhandled edge cases, resource leaks, incorrect state transitions.\n\n3. **For each potential bug**, generate a bug report using the template above, with the likely trigger scenario and recommended fix filled in.\n\n---\n\n## Phase 2C: Verify Mode\n\nRead `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md`. Extract the reproduction steps and expected result.\n\n1. **Re-run reproduction steps** — use Grep\u002FGlob to check whether the root cause code path still exists as described. If the fix removed or changed it, note the change.\n2. **Run the related test** — if the bug's system has a test file in `tests\u002F`, run it via Bash and report pass\u002Ffail.\n3. **Check for regression** — grep the codebase for any new occurrence of the pattern that caused the bug.\n\nProduce a verification verdict:\n\n- **VERIFIED FIXED** — reproduction steps no longer produce the bug; related tests pass\n- **STILL PRESENT** — bug reproduces as described; fix did not resolve the issue\n- **CANNOT VERIFY** — automated checks inconclusive; manual playtest required\n\nAsk: \"May I update `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md` to set Status: Verified Fixed \u002F Still Present \u002F Cannot Verify?\"\n\nIf STILL PRESENT: reopen the bug, set Status back to Open, and suggest re-running `\u002Fhotfix [BUG-ID]`.\n\n---\n\n## Phase 2D: Close Mode\n\nRead `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md`. Confirm Status is `Verified Fixed` before closing. If status is anything else, stop: \"Bug [ID] must be Verified Fixed before it can be closed. Run `\u002Fbug-report verify [BUG-ID]` first.\"\n\nAppend a closure record to the bug file:\n\n```markdown\n## Closure Record\n**Closed**: [date]\n**Resolution**: Fixed — [one-line description of what was changed]\n**Fix commit \u002F PR**: [if known]\n**Verified by**: qa-tester\n**Closed by**: [user]\n**Regression test**: [test file path, or \"Manual verification\"]\n**Status**: Closed\n```\n\nUpdate the top-level `**Status**: Open` field to `**Status**: Closed`.\n\nAsk: \"May I update `production\u002Fqa\u002Fbugs\u002F[BUG-ID].md` to mark it Closed?\"\n\nAfter closing, check `production\u002Fqa\u002Fbug-triage-*.md` — if the bug appears in an open triage report, note: \"Bug [ID] is referenced in the triage report. Run `\u002Fbug-triage` to refresh the open bug count.\"\n\n---\n\n## Phase 3: Save Report\n\nPresent the completed bug report(s) to the user.\n\nAsk: \"May I write this to `production\u002Fqa\u002Fbugs\u002FBUG-[NNNN].md`?\"\n\nIf yes, write the file, creating the directory if needed. Verdict: **COMPLETE** — bug report filed.\n\nIf no, stop here. Verdict: **BLOCKED** — user declined write.\n\n---\n\n## Phase 4: Next Steps\n\nAfter saving, suggest based on mode:\n\n**After filing (Description\u002FAnalyze mode):**\n- Run `\u002Fbug-triage` to prioritize alongside existing open bugs\n- If S1 or S2: run `\u002Fhotfix [BUG-ID]` for emergency fix workflow\n\n**After fixing the bug (developer confirms fix is in):**\n- Run `\u002Fbug-report verify [BUG-ID]` — confirm the fix actually works before closing\n- Never mark a bug closed without verification — a fix that doesn't verify is still Open\n\n**After verify returns VERIFIED FIXED:**\n- Run `\u002Fbug-report close [BUG-ID]` — write the closure record and update status\n- Run `\u002Fbug-triage` to refresh the open bug count and remove it from the active list\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"user-invocable":26},"Read, Glob, Grep, Write","[description] | analyze [path-to-file]",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fbug-report",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":36,"prompt":46,"zipAvailable":26},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill bug-report",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill bug-report",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill bug-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbug-report\u002FSKILL.md",[],[49,56,63,70,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"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},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\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},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\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":74,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]