Loading...
Loading...
Found 1,437 Skills
Set up GitHub Actions workflows for CI/CD with automated testing, linting, and deployment for Python/UV projects. Use when creating CI pipelines, automating tests, or setting up deployment workflows.
Set up complete GitHub Copilot configuration for a new project based on technology stack
Use when syncing skills from local folders, GitHub URLs, or skillsmp.com pages to multiple AI coding tool directories
Outputs markdown digests and CSV exports for GitHub issues and PRs. Use when creating status reports, weekly updates, stakeholder briefings, generating GitHub comment digests, tracking initiative health. Do not use when release gates/readiness - use release-health-gates. DO NOT use when: project planning - use spec-kit:speckit-orchestrator.
Feature review and prioritization with RICE/WSJF/Kano scoring. Creates GitHub issues for suggestions. feature review, prioritization, RICE, WSJF, roadmap, backlog Use when: reviewing features or suggesting new features DO NOT use when: evaluating single feature scope - use scope-guard.
Check if a newer version of groove is available on GitHub.
Automatically collect and summarize daily AI industry news, trends, and hot topics from platforms like GitHub (trending repos), X/Twitter (AI influencers/hashtags), and AI news aggregators. Use this skill when the user asks for "today's AI news", "AI industry updates", "what's trending in AI", or wants a daily digest of AI developments.
Expert guide for creating GitHub Copilot customization files in VS Code: custom instructions (.instructions.md), prompt files (.prompt.md), custom agents (.agent.md), agent skills (SKILL.md), hooks (JSON), and agent plugins. Use this skill whenever the user asks about customizing Copilot behavior, creating reusable AI workflows, writing copilot-instructions.md, building custom chat agents, automating Copilot tasks with prompt files, or setting up agent skills and hooks in VS Code. Also trigger when the user asks which Copilot customization type to use for a given scenario — always start with the decision matrix below.
Generates detailed, architect-quality GitHub issues from short instructions. Analyzes the project's actual stack, architecture, and codebase before writing. Detects duplicate issues with intelligent multi-strategy search, validates and creates labels, enforces title conventions, controls scope, and publishes via `gh` CLI with robust error handling. Use this skill whenever the user wants to create a GitHub issue, report a bug, propose a feature, request a refactor, or file any kind of technical issue — even if they just say something brief like "we need to fix the auth flow" or "create an issue for X". Also triggers on: "open an issue", "file a bug", "I want to propose...", "add this to the backlog", "gh issue", or any request that implies creating a trackable work item on GitHub.
Check GitHub Actions workflow status after git push using gh CLI. Reports CI status, identifies failing jobs, and suggests local reproduction commands. Use after "git push", when user asks about CI status, workflow failures, or build results. Use for "check CI", "workflow status", "actions failing", or "build broken". Do NOT use for local linting (use code-linting), debugging test failures locally (use systematic-debugging), or setting up new workflows.
GitHub PR review threads—KEEP/DISCARD triage, replies, KEEP-only code changes, lint/test/push. Open PRs only; not for creating PRs (create-pr-jp).
Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. Trigger for requests to use gh, manage GitHub repos, PRs, or issues from the CLI.