Loading...
Loading...
Found 2,779 Skills
Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Also trigger when the user wants feedback on code changes, wants to approve or request changes on a PR, or asks to review someone's contribution.
Pre-build reality check for AI coding agents — scan GitHub, HN, npm, PyPI, Product Hunt to validate ideas before building
Create, triage, label, assign GitHub issues via gh or REST.
Work with Git repositories from the command line.
Audit GitHub Actions workflow efficiency and recommend fixes to reduce CI minutes and costs.
Scan GitHub Actions workflow files for security vulnerabilities by reading the YAML and reporting findings directly — no external tools, no installation, no shell execution. Use this skill whenever the user shares a `.github/workflows/` file, pastes workflow YAML, asks for a CI/CD security review, mentions `pull_request_target`, `workflow_run`, action pinning, `GITHUB_TOKEN` permissions, pwn requests, template injection, cache poisoning, secret exfiltration, supply chain risk, or any GitHub Actions hardening topic. Also trigger when the user is hardening an OSS repo, doing a CI/CD red team assessment, evaluating a target for supply-chain scanning, or writing publicly about CI/CD security. Bias toward triggering this skill rather than answering from memory — CI/CD security defaults are wrong almost everywhere and the rules are unintuitive.
Review one pull request through a standalone, progressively disclosed workflow. Use when the user asks to review a PR, audit a pull request, prepare GitHub review comments, draft request-changes feedback, write a PR review file, or optionally post approved review comments. This skill handles exactly one PR; ask the user to choose one PR when multiple PR URLs are supplied.
Automates codebase environment configuration, troubleshooting, and repair. When non-technical users (editors, business personnel, operations staff) get a repository and say things like "it won't run", "how to start", "how to configure the environment", "help me set up the codebase", "initialize the project", "commit code", "what to do about conflicts", it automatically reads ONBOARDING.md, diagnoses environment gaps, fixes dependencies, verifies runnability, and safely completes git operations. It is also used by technical users to quickly standardize the setup process for new repositories (SessionStart hook, PII Guard, history sanitization, project-isolated API keys). This skill is triggered whenever users mention terms like "environment", "configuration", "won't run", "setup", "start", "clone", "how to run", "dependencies", "is it installed", "commit code", "merge conflict", "push failed".
Use when you need to analyze git diffs or pull requests to understand what changed, affected components, and risks
Manage repositories, check pipelines, review merge requests, and monitor CI/CD on GitLab
Detect exposed secrets, API keys, credentials, and tokens in code. Use before commits, on file saves, or when security is mentioned. Prevents accidental secret exposure. Triggers on file changes, git commits, security checks, .env file modifications.
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an