github
Automatiza la interacción con GitHub usando el CLI gh para issues, PRs y commits.
Install
mkdir -p .claude/skills/github-dslc-io && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14270" && unzip -o skill.zip -d .claude/skills/github-dslc-io && rm skill.zipInstalls to .claude/skills/github-dslc-io
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
GitHub workflows using the `gh` CLI, including viewing issues/PRs and commit message conventions. Use when interacting with GitHub in any way, such as viewing, creating, or editing issues and pull requests, making commits, or running any `gh` command.Key capabilities
- →View GitHub issues and pull requests using the `gh` CLI
- →Create new issues and pull requests via CLI
- →Follow conventional commit message guidelines
- →Close issues automatically through commit messages
- →Navigate GitHub resources from the terminal
How it works
It uses the `gh` command-line interface to interact with GitHub, allowing users to view and manage issues and pull requests. It also enforces commit message conventions for better project hygiene and issue linking.
Inputs & outputs
When to use github
- →Ver listado de PRs abiertos
- →Cerrar issues mediante commits
- →Listar issues pendientes
- →Trabajar con GitHub desde la terminal
About this skill
GitHub
Use gh CLI, not web URLs: gh issue view 123, gh issue list, gh pr view 456, gh pr list.
Commit messages
Conventional commits; backtick-quote function names; close issues in body with - Closes #N.
feat: add `create_skill()`
Generates a new skill directory with a SKILL.md template.
- Closes #3
When not to use it
- →When the user prefers to interact with GitHub solely through the web interface
- →When the `gh` CLI is not installed or authenticated
Prerequisites
Limitations
- →It requires the `gh` CLI to be installed.
- →It requires an authenticated GitHub session.
- →It enforces specific commit message conventions.
How it compares
This skill provides a CLI-centric workflow for GitHub interactions and enforces specific commit message conventions, offering an alternative to web-based or less structured approaches.
Compared to similar skills
github side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| github (this skill) | 0 | 5mo | No flags | Beginner |
| github-workflow-automation | 11 | 4mo | Review | Advanced |
| testing-workflow | 16 | 11mo | Review | Intermediate |
| github-actions-templates | 7 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dslc-io
View all by dslc-io →You might also like
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
glab
NikiforovAll
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
create-pr
n8n-io
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
gh-fix-ci
openai
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.