pr-hotfix
Bypasses standard PR workflows for quick, safe fixes.
Install
mkdir -p .claude/skills/pr-hotfix && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16740" && unzip -o skill.zip -d .claude/skills/pr-hotfix && rm skill.zipInstalls to .claude/skills/pr-hotfix
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.
Commit and push a small fix directly to main, bypassing the PR workflow.Key capabilities
- →Commit staged/unstaged changes
- →Push changes directly to main
- →Check current branch status
- →Review recent commit style
- →Stage relevant changed files by name
- →Report commit hash and push success
How it works
The skill checks the current branch, reviews changes, stages specific files, commits them with a conventional message, and pushes directly to the `main` branch.
Inputs & outputs
When to use pr-hotfix
- →Fix typos in documentation
- →Update configuration files
- →Apply emergency small fixes
About this skill
Commit the current staged/unstaged changes directly to main. Use only for small, safe fixes (docs, config, typos) that do not need review.
Steps
- Run
git branch --show-current. If the current branch is notmain, stop and tell the user to switch tomainfirst or use/pr-newinstead. - Run
git statusandgit diffto understand exactly what has changed. - Run
git log --oneline -5to see recent commit style. - Stage all relevant changed files by name (never use
git add -Aorgit add .). - Commit with a conventional commit message that explains the why, not just the what. Do not append any co-author trailer — the commit message must end after the body with no additional lines like
Co-Authored-By: .... - Push directly to main:
git push origin main - Report the commit hash and confirm the push succeeded.
When not to use it
- →If the current branch is not `main`.
- →For large or complex changes that require a PR workflow.
- →For changes that need review.
Limitations
- →The skill is only for small, safe fixes.
- →The skill requires the current branch to be `main`.
- →The skill does not support `git add -A` or `git add .`.
How it compares
This skill bypasses the standard PR workflow for small, safe fixes by committing and pushing directly to `main`, which is faster than a full review process.
Compared to similar skills
pr-hotfix side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr-hotfix (this skill) | 0 | 1mo | Review | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| openspec-onboard | 10 | 6mo | Review | Beginner |
| codex-cli-bridge | 9 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-sync
KyleKing
Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.