[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76RYC42TMJZJBZNAM0H59DD":3,"skill-same:01M76RYC42TMJZJBZNAM0H59DD":48},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M76RYC42TMJZJBZNAM0H59DD","github-ops",null,"GitHub repository operations, automation, and management. Issue triage, PR management, CI\u002FCD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.","AlexanderNarbaev\u002Fagi","AlexanderNarbaev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F33544956?v=4","01M755ZKB1JJ26ZBNZSDJ4C0TV","01M755ZKBX072HZMHVQBWK7MK7",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fgithub-ops\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: github-ops\ndescription: GitHub repository operations, automation, and management. Issue triage, PR management, CI\u002FCD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git commands.\nused-by:\n  - \"Code\"\n  - \"General\"\nschemaVersion: \"v0.1\"\n---\n\n# GitHub Operations\n\nManage GitHub repositories with a focus on community health, CI reliability, and contributor experience.\n\n## When to Activate\n\n- Triaging issues (classifying, labeling, responding, deduplicating)\n- Managing PRs (review status, CI checks, stale PRs, merge readiness)\n- Debugging CI\u002FCD failures\n- Preparing releases and changelogs\n- Monitoring Dependabot and security alerts\n- Managing contributor experience on open-source projects\n- User says \"check GitHub\", \"triage issues\", \"review PRs\", \"merge\", \"release\", \"CI is broken\"\n\n## Tool Requirements\n\n- **gh CLI** for all GitHub API operations\n- Repository access configured via `gh auth login`\n\n## Issue Triage\n\nClassify each issue by type and priority:\n\n**Types:** bug, feature-request, question, documentation, enhancement, duplicate, invalid, good-first-issue\n\n**Priority:** critical (breaking\u002Fsecurity), high (significant impact), medium (nice to have), low (cosmetic)\n\n### Triage Workflow\n\n1. Read the issue title, body, and comments\n2. Check if it duplicates an existing issue (search by keywords)\n3. Apply appropriate labels via `gh issue edit --add-label`\n4. For questions: draft and post a helpful response\n5. For bugs needing more info: ask for reproduction steps\n6. For good first issues: add `good-first-issue` label\n7. For duplicates: comment with link to original, add `duplicate` label\n\n```bash\n# Search for potential duplicates\ngh issue list --search \"keyword\" --state all --limit 20\n\n# Add labels\ngh issue edit \u003Cnumber> --add-label \"bug,high-priority\"\n\n# Comment on issue\ngh issue comment \u003Cnumber> --body \"Thanks for reporting. Could you share reproduction steps?\"\n```\n\n## PR Management\n\n### Review Checklist\n\n1. Check CI status: `gh pr checks \u003Cnumber>`\n2. Check if mergeable: `gh pr view \u003Cnumber> --json mergeable`\n3. Check age and last activity\n4. Flag PRs >5 days with no review\n5. For community PRs: ensure they have tests and follow conventions\n\n### Stale Policy\n\n- Issues with no activity in 14+ days: add `stale` label, comment asking for update\n- PRs with no activity in 7+ days: comment asking if still active\n- Auto-close stale issues after 30 days with no response (add `closed-stale` label)\n\n```bash\n# Find stale issues (no activity in 14+ days)\ngh issue list --label \"stale\" --state open\n\n# Find PRs with no recent activity\ngh pr list --json number,title,updatedAt --jq '.[] | select(.updatedAt \u003C \"2026-03-01\")'\n```\n\n## CI\u002FCD Operations\n\nWhen CI fails:\n\n1. Check the workflow run: `gh run view \u003Crun-id> --log-failed`\n2. Identify the failing step\n3. Check if it is a flaky test vs real failure\n4. For real failures: identify the root cause and suggest a fix\n5. For flaky tests: note the pattern for future investigation\n\n```bash\n# List recent failed runs\ngh run list --status failure --limit 10\n\n# View failed run logs\ngh run view \u003Crun-id> --log-failed\n\n# Re-run a failed workflow\ngh run rerun \u003Crun-id> --failed\n```\n\n## Release Management\n\nWhen preparing a release:\n\n1. Check all CI is green on main\n2. Review unreleased changes: `gh pr list --state merged --base main`\n3. Generate changelog from PR titles\n4. Create release: `gh release create`\n\n```bash\n# List merged PRs since last release\ngh pr list --state merged --base main --search \"merged:>2026-03-01\"\n\n# Create a release\ngh release create v1.2.0 --title \"v1.2.0\" --generate-notes\n\n# Create a pre-release\ngh release create v1.3.0-rc1 --prerelease --title \"v1.3.0 Release Candidate 1\"\n```\n\n## Security Monitoring\n\n```bash\n# Check Dependabot alerts\ngh api repos\u002F{owner}\u002F{repo}\u002Fdependabot\u002Falerts --jq '.[].security_advisory.summary'\n\n# Check secret scanning alerts\ngh api repos\u002F{owner}\u002F{repo}\u002Fsecret-scanning\u002Falerts --jq '.[].state'\n\n# Review and auto-merge safe dependency bumps\ngh pr list --label \"dependencies\" --json number,title\n```\n\n- Review and auto-merge safe dependency bumps\n- Flag any critical\u002Fhigh severity alerts immediately\n- Check for new Dependabot alerts weekly at minimum\n\n## Quality Gate\n\nBefore completing any GitHub operations task:\n- all issues triaged have appropriate labels\n- no PRs older than 7 days without a review or comment\n- CI failures have been investigated (not just re-run)\n- releases include accurate changelogs\n- security alerts are acknowledged and tracked\n","# GitHub Operations\n\nManage GitHub repositories with a focus on community health, CI reliability, and contributor experience.\n\n## When to Activate\n\n- Triaging issues (classifying, labeling, responding, deduplicating)\n- Managing PRs (review status, CI checks, stale PRs, merge readiness)\n- Debugging CI\u002FCD failures\n- Preparing releases and changelogs\n- Monitoring Dependabot and security alerts\n- Managing contributor experience on open-source projects\n- User says \"check GitHub\", \"triage issues\", \"review PRs\", \"merge\", \"release\", \"CI is broken\"\n\n## Tool Requirements\n\n- **gh CLI** for all GitHub API operations\n- Repository access configured via `gh auth login`\n\n## Issue Triage\n\nClassify each issue by type and priority:\n\n**Types:** bug, feature-request, question, documentation, enhancement, duplicate, invalid, good-first-issue\n\n**Priority:** critical (breaking\u002Fsecurity), high (significant impact), medium (nice to have), low (cosmetic)\n\n### Triage Workflow\n\n1. Read the issue title, body, and comments\n2. Check if it duplicates an existing issue (search by keywords)\n3. Apply appropriate labels via `gh issue edit --add-label`\n4. For questions: draft and post a helpful response\n5. For bugs needing more info: ask for reproduction steps\n6. For good first issues: add `good-first-issue` label\n7. For duplicates: comment with link to original, add `duplicate` label\n\n```bash\n# Search for potential duplicates\ngh issue list --search \"keyword\" --state all --limit 20\n\n# Add labels\ngh issue edit \u003Cnumber> --add-label \"bug,high-priority\"\n\n# Comment on issue\ngh issue comment \u003Cnumber> --body \"Thanks for reporting. Could you share reproduction steps?\"\n```\n\n## PR Management\n\n### Review Checklist\n\n1. Check CI status: `gh pr checks \u003Cnumber>`\n2. Check if mergeable: `gh pr view \u003Cnumber> --json mergeable`\n3. Check age and last activity\n4. Flag PRs >5 days with no review\n5. For community PRs: ensure they have tests and follow conventions\n\n### Stale Policy\n\n- Issues with no activity in 14+ days: add `stale` label, comment asking for update\n- PRs with no activity in 7+ days: comment asking if still active\n- Auto-close stale issues after 30 days with no response (add `closed-stale` label)\n\n```bash\n# Find stale issues (no activity in 14+ days)\ngh issue list --label \"stale\" --state open\n\n# Find PRs with no recent activity\ngh pr list --json number,title,updatedAt --jq '.[] | select(.updatedAt \u003C \"2026-03-01\")'\n```\n\n## CI\u002FCD Operations\n\nWhen CI fails:\n\n1. Check the workflow run: `gh run view \u003Crun-id> --log-failed`\n2. Identify the failing step\n3. Check if it is a flaky test vs real failure\n4. For real failures: identify the root cause and suggest a fix\n5. For flaky tests: note the pattern for future investigation\n\n```bash\n# List recent failed runs\ngh run list --status failure --limit 10\n\n# View failed run logs\ngh run view \u003Crun-id> --log-failed\n\n# Re-run a failed workflow\ngh run rerun \u003Crun-id> --failed\n```\n\n## Release Management\n\nWhen preparing a release:\n\n1. Check all CI is green on main\n2. Review unreleased changes: `gh pr list --state merged --base main`\n3. Generate changelog from PR titles\n4. Create release: `gh release create`\n\n```bash\n# List merged PRs since last release\ngh pr list --state merged --base main --search \"merged:>2026-03-01\"\n\n# Create a release\ngh release create v1.2.0 --title \"v1.2.0\" --generate-notes\n\n# Create a pre-release\ngh release create v1.3.0-rc1 --prerelease --title \"v1.3.0 Release Candidate 1\"\n```\n\n## Security Monitoring\n\n```bash\n# Check Dependabot alerts\ngh api repos\u002F{owner}\u002F{repo}\u002Fdependabot\u002Falerts --jq '.[].security_advisory.summary'\n\n# Check secret scanning alerts\ngh api repos\u002F{owner}\u002F{repo}\u002Fsecret-scanning\u002Falerts --jq '.[].state'\n\n# Review and auto-merge safe dependency bumps\ngh pr list --label \"dependencies\" --json number,title\n```\n\n- Review and auto-merge safe dependency bumps\n- Flag any critical\u002Fhigh severity alerts immediately\n- Check for new Dependabot alerts weekly at minimum\n\n## Quality Gate\n\nBefore completing any GitHub operations task:\n- all issues triaged have appropriate labels\n- no PRs older than 7 days without a review or comment\n- CI failures have been investigated (not just re-run)\n- releases include accurate changelogs\n- security alerts are acknowledged and tracked\n",{"name":5,"used-by":23,"description":7,"schemaVersion":26},[24,25],"Code","General","v0.1","main","7709dc9e5ebd3bd641124ad2a3f6bb053ac2dab6",".veai\u002Fskills\u002Fgithub-ops",0,"https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev","2026-11-15 04:35:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add AlexanderNarbaev\u002Fagi --skill github-ops",{"tool":40,"command":41},"bunx","bunx skills add AlexanderNarbaev\u002Fagi --skill github-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add AlexanderNarbaev\u002Fagi --skill github-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fgithub-ops\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M76RZHYHMGE1WP9JBCMNA801","springboot-patterns","Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fspringboot-patterns\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M76RZE6JNZH5HV7Q8JM7R0PN","search-first","Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fsearch-first\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M76RZBV42EMQV77H7GMFY4AJ","scholar-evaluation","Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fscholar-evaluation\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M76RZ97GC3XAY48H126C30PM","redis-patterns","Redis data structure patterns, caching strategies, distributed locks, rate limiting, pub\u002Fsub, and connection management for production applications.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fredis-patterns\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M76RZ528FANTKX7Q9XR0CXM7","react-patterns","React 18\u002F19 patterns including hooks discipline, server\u002Fclient component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Freact-patterns\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M76RZ1244PZQRQV5HBQ4PVYQ","query-patterns","SQL patterns, relational database design, query optimization, transactions, analytics, and dialect-aware best practices.","https:\u002F\u002Fgithub.com\u002FAlexanderNarbaev\u002Fagi\u002Fblob\u002Fmain\u002F.veai\u002Fskills\u002Fquery-patterns\u002FSKILL.md",[],[]]