Explorar skills

Comprehensive GitHub code review with AI-powered swarm coordination

Spec-Driven Development (SDD) methodology based on GitHub's SpecKit.

Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.

GitHub Issue 处理协作流程。当用户收到 issue 需要分析和回复时使用。通过"诊断 → 定性 → 决策 → 回复"四步法，从一个 issue 产出准确的根因分析和得体的用户回复，避免误判问题类型或回复不专业。

GitHubのプルリクエスト（PR）を作成する際に使用します。変更のコミット、プッシュ、PR作成を含む完全なワークフローを日本語で実行します。「PRを作って」「プルリクエストを作成」「pull requestを作成」などのリクエストで自動的に起動します。

-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.

GitHub issues management assistant for Logseq Template Graph. Analyzes issues, triages with labels, plans implementations, generates responses, creates PRs, and manages issue lifecycle. Use when handling bug reports, feature requests, questions, or coordinating development through GitHub issues.

Build applications powered by GitHub Copilot using the Copilot SDK. Use when creating programmatic integrations with Copilot across Node.js/TypeScript, Python, Go, or .NET. Covers session management, custom tools, streaming, hooks, MCP servers, BYOK providers, session persistence, and custom agents. Requires GitHub Copilot CLI installed and a GitHub Copilot subscription (unless using BYOK).

Set up CI/CD pipelines with GitHub Actions. Use when creating new projects, adding automation, or when manual verification becomes bottleneck. Covers lint, test, build, deploy automation.

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management

READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance. USE WHEN: Asking about status, active threads, workflow state, or needing context at session start. DO NOT USE WHEN: Claiming issues (use ghe-claim), posting checkpoints (ghe-checkpoint), transitioning phases (ghe-transition), or needing detailed reports (ghe-repor

Triage FiftyOne GitHub issues by validating status, categorizing resolution, and generating standardized responses. Use when reviewing issues to determine if fixed, won't fix, not reproducible, no longer relevant, or still valid.