github-operations
Standardized workflow for managing GitHub issues, pull requests, and releases.
Install
mkdir -p .claude/skills/github-operations && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10751" && unzip -o skill.zip -d .claude/skills/github-operations && rm skill.zipInstalls to .claude/skills/github-operations
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.
Guide GitHub issue, pull request, and release operations for this repository.Key capabilities
- →Guide issue creation with descriptive titles and labels
- →Provide guidelines for pull request titles using conventional commit format
- →Ensure pull requests link to related issues
- →Manage releases with semantic versioning tags
- →Include changelogs in releases
- →Coordinate facilitator guide updates with releases
How it works
The skill provides a set of guidelines for GitHub operations, including issue labeling, pull request formatting, and release tagging, to maintain repository quality.
Inputs & outputs
When to use github-operations
- →Opening pull requests
- →Triage github issues
- →Managing software releases
About this skill
GitHub Operations Skill
Purpose
Guide GitHub issue, pull request, and release operations for this repository.
When to Use
- Creating or triaging issues
- Opening or reviewing pull requests
- Managing releases or milestones
Guidelines
Issues
- Use descriptive titles:
[Challenge X] Description of problem - Label with:
bug,enhancement,documentation,facilitator - Include reproduction steps for bugs
- Reference related challenge numbers
Pull Requests
- Use conventional commit format in PR title
- Link related issues with
Closes #NorFixes #N - Request review from repository maintainers
- Ensure CI passes before merging (Astro build + markdownlint)
Releases
- Tag releases with semantic versioning:
v1.0.0 - Include changelog summarising content and structural changes
- Coordinate with facilitator guide updates
Constraints
- Do not force-push to
main - Do not merge PRs with failing CI checks
- Do not include facilitator-only content in public issue descriptions
When not to use it
- →When performing operations outside of GitHub issues, pull requests, or releases
- →When not adhering to conventional commit formats or semantic versioning
Limitations
- →Does not allow force-pushing to `main`
- →Prohibits merging PRs with failing CI checks
- →Excludes facilitator-only content from public issue descriptions
How it compares
This skill enforces standardized GitHub operations, ensuring consistency across issues, PRs, and releases, unlike an unguided approach.
Compared to similar skills
github-operations side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| github-operations (this skill) | 0 | 4mo | No flags | Beginner |
| agent-project-board-sync | 0 | 6mo | Review | Intermediate |
| release-version | 0 | 6mo | Review | Intermediate |
| release | 0 | 4mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jonathan-vella
View all by jonathan-vella →You might also like
agent-project-board-sync
ruvnet
Agent skill for project-board-sync - invoke with $agent-project-board-sync
release-version
corvo007
Use when releasing a new version - guides through version bump, changelog generation, commit grouping, tagging, and GitHub CI tracking. Triggers on "发布新版本", "release", "发版", or version release requests.
release
JustLookAtNow
自动化项目的版本发布流程，包括版本号自增、ChangeLog 提取与汇总、代码提交、打标签以及推送到远程仓库。
ship
devkanro
>-
land
All-The-Vibes
Session completion protocol - the opposite of "takeoff". Use this skill whenever the user says "land", "/land", "land the plane", "land it", "let's land", "land this", "bring it in", "wrap it up", "land the plan", "land plane", "time to land", "ok land", "go ahead and land", or any variation that si
maintainer-label-system
InternationalColorConsortium
>