[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F07F5MFJXYV16B5ME3HA2H":3,"skill-same:01M7F07F5MFJXYV16B5ME3HA2H":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F07F5MFJXYV16B5ME3HA2H","gha",null,"Analyze GitHub Actions failures and identify root causes","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-技能与代理开发\u002Fgha\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: gha\ndescription: Analyze GitHub Actions failures and identify root causes\nargument-hint: \u003Curl>\n---\n\nInvestigate this GitHub Actions URL: $ARGUMENTS\n\nUse the gh CLI to analyze this workflow run. Your investigation should:\n\n1. **Get basic info & identify actual failure**:\n   - What workflow\u002Fjob failed, when, and on which commit?\n   - CRITICAL: Read the full logs carefully to find what SPECIFICALLY caused the exit code 1\n   - Distinguish between warnings\u002Fnon-fatal errors vs actual failures\n   - Look for patterns like \"failing:\", \"fatal:\", or script logic that determines when to exit 1\n   - If you see both \"non-fatal\" and \"fatal\" errors, focus on what actually caused the failure\n\n2. **Check flakiness**: Check the past 10-20 runs of THE EXACT SAME failing job:\n   - IMPORTANT: If a workflow has multiple jobs, you must check history for the SPECIFIC JOB that failed, not just the workflow\n   - Use `gh run list --workflow=\u003Cworkflow-name>` to get run IDs, then `gh run view \u003Crun-id> --json jobs` to check the specific job's status\n   - Is this a one-time failure or recurring pattern for THIS SPECIFIC JOB?\n   - What's the success rate for THIS JOB recently?\n   - When did THIS JOB last pass?\n\n3. **Identify breaking commit** (if there's a pattern of failures for the specific job):\n   - Find the first run where THIS SPECIFIC JOB failed and the last run where it passed\n   - Identify the commit that introduced the failure\n   - Verify by checking: does THIS JOB fail in ALL runs after that commit? Does it pass in ALL runs before?\n   - If verified, report the breaking commit with high confidence\n\n4. **Root cause**: Based on logs, history, and any breaking commit, what's the likely cause?\n   - Focus on what ACTUALLY caused the failure (not just any errors you see)\n   - Verify your hypothesis against the logs and failure logic\n\n5. **Check for existing fix PRs**: Search for open PRs that might already address this issue:\n   - Use `gh pr list --state open --search \"\u003Ckeywords>\"` with relevant error messages or file names\n   - Check if any open PR modifies the failing file\u002Fworkflow\n   - If a fix PR exists, note it in your report and skip the recommendation section\n\nWrite a final report with:\n- Summary of failure (what specifically triggered the exit code 1)\n- Flakiness assessment (one-time vs recurring, success rate)\n- Breaking commit (if identified and verified)\n- Root cause analysis (based on the ACTUAL failure trigger)\n- Existing fix PR (if found - include PR number and link)\n- Recommendation (skip if fix PR already exists)\n","Investigate this GitHub Actions URL: $ARGUMENTS\n\nUse the gh CLI to analyze this workflow run. Your investigation should:\n\n1. **Get basic info & identify actual failure**:\n   - What workflow\u002Fjob failed, when, and on which commit?\n   - CRITICAL: Read the full logs carefully to find what SPECIFICALLY caused the exit code 1\n   - Distinguish between warnings\u002Fnon-fatal errors vs actual failures\n   - Look for patterns like \"failing:\", \"fatal:\", or script logic that determines when to exit 1\n   - If you see both \"non-fatal\" and \"fatal\" errors, focus on what actually caused the failure\n\n2. **Check flakiness**: Check the past 10-20 runs of THE EXACT SAME failing job:\n   - IMPORTANT: If a workflow has multiple jobs, you must check history for the SPECIFIC JOB that failed, not just the workflow\n   - Use `gh run list --workflow=\u003Cworkflow-name>` to get run IDs, then `gh run view \u003Crun-id> --json jobs` to check the specific job's status\n   - Is this a one-time failure or recurring pattern for THIS SPECIFIC JOB?\n   - What's the success rate for THIS JOB recently?\n   - When did THIS JOB last pass?\n\n3. **Identify breaking commit** (if there's a pattern of failures for the specific job):\n   - Find the first run where THIS SPECIFIC JOB failed and the last run where it passed\n   - Identify the commit that introduced the failure\n   - Verify by checking: does THIS JOB fail in ALL runs after that commit? Does it pass in ALL runs before?\n   - If verified, report the breaking commit with high confidence\n\n4. **Root cause**: Based on logs, history, and any breaking commit, what's the likely cause?\n   - Focus on what ACTUALLY caused the failure (not just any errors you see)\n   - Verify your hypothesis against the logs and failure logic\n\n5. **Check for existing fix PRs**: Search for open PRs that might already address this issue:\n   - Use `gh pr list --state open --search \"\u003Ckeywords>\"` with relevant error messages or file names\n   - Check if any open PR modifies the failing file\u002Fworkflow\n   - If a fix PR exists, note it in your report and skip the recommendation section\n\nWrite a final report with:\n- Summary of failure (what specifically triggered the exit code 1)\n- Flakiness assessment (one-time vs recurring, success rate)\n- Breaking commit (if identified and verified)\n- Root cause analysis (based on the ACTUAL failure trigger)\n- Existing fix PR (if found - include PR number and link)\n- Recommendation (skip if fix PR already exists)\n",{"name":5,"description":7,"argument-hint":24},"\u003Curl>","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fgha",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill gha",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill gha",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill gha","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgha\u002FSKILL.md",true,[],[48,55,60,67,74,81],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"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",[],[],{"skillNo":56,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"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",[],[]]