一键导入
git-workflow
// Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
// Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
OwnPilot official general skill for drafting, editing, restructuring, and reviewing long-form documents, reports, proposals, policies, and documentation. Use when the user asks to create or improve a document.
OwnPilot official general skill for converting rough meeting notes, transcripts, and call summaries into decisions, action items, owners, risks, and follow-ups. Use when the user provides meeting content or asks for notes.
OwnPilot official general skill for creating slide outlines, executive narratives, speaker notes, and presentation critiques. Use when the user asks for slides, a deck, a pitch, or a narrative.
OwnPilot official general skill for turning mixed research material into concise, sourced briefs, comparisons, decisions, and next steps. Use when the user asks to research, compare options, summarize sources, or prepare a recommendation.
OwnPilot official general skill for planning spreadsheet models, analyzing CSV or table data, explaining formulas, checking data quality, and designing reports. Use when the user works with spreadsheet-like data.
Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests.
| name | git-workflow |
| description | Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices. |
| license | MIT |
| metadata | {"author":"ownpilot","version":"1.0.0"} |
| allowed-tools | Bash(git:*) |
You are an expert in Git version control. Follow these guidelines when helping with Git operations.
Use Conventional Commits format:
<type>(<scope>): <description>
[optional body]
[optional footer]
Types: feat, fix, refactor, docs, test, chore, perf, ci, build
Examples:
feat(auth): add JWT refresh token rotationfix(api): handle null response from payment gatewayrefactor(db): extract repository base classDefault: GitHub Flow (simple, PR-based)
main — always deployablefeature/<name> — short-lived feature branchesfix/<name> — bug fix branchesrelease/<version> — release prep (if needed)Before submitting a PR:
When the user asks you to:
git checkout -b feature/<name>git add <specific-files> over git add .git commit --amend (only if not pushed)git rebase -i HEAD~N (only on local branches)git reset --soft HEAD~1 (keeps changes staged)git cherry-pick <hash> (apply specific commit to current branch)