git-workflows
0
creating-commits
Use before EVERY git commit - no exceptions. Enforces pre-commit quality checks, atomic commits, and conventional commit format to prevent hook failures and maintain clean history
zookanalytics
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
git-workflows
0
switch-feature
Commit or stash current work, then switch to another existing worktree. Use when switching between features or stories, ensures changes are saved before switching.
michael-menard
devops
git-workflows
0
sharing-skills
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository
nimeshgurung
devops
git-workflows
0
commit-push-pr-workflow
Standardized commit + push + PR workflow. Use when the user asks to commit/push/open PR to ensure checks run, messages are consistent, and pushes/force-pushes are handled safely.
yiyousiow000814
devops
git-workflows
0
finishing-a-development-branch
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
Ramblurr
devops
git-workflows
0
github-release
Create GitHub releases with version tags, release notes, and changelog generation from merged PRs
do-ops885
devops
git-workflows
0
workbranch
This skill should be used when starting work on a "new feature", "bug fix", "branch", "isolated development", when the user asks to "create a worktree", "set up a branch for development", "work on feature X", "fix bug Y", when discussing git worktree management, or when recovering from mistakes like "made changes on main by mistake", "accidentally committed to main", "forgot to create a worktree", "need to move changes to a branch". Provides git worktree workflow that should be the DEFAULT approach for all feature and bugfix development.
thirteen37
devops
git-workflows
0
pr-restructure
Clean up messy commit history into atomic commits before merge. Use when user wants to restructure PR commit history based on final diff. Triggers include: - Korean: "PR 히스토리 정리해줘", "커밋 히스토리 정리", "커밋 깔끔하게" - English: "clean up commit history", "restructure commits", "organize commits" - Context: User has messy commits (WIP, typo fixes) and wants atomic commit structure
furiosa-ai
devops
git-workflows
0
git-safety
Git 操作安全与规范。强制要求使用 git 原生命令处理受控文件，防止丢失索引或产生冗余变更。当 Agent 尝试移动、重命名或删除文件时触发。
ab300819
devops
git-workflows
0
specimin-wrap
Squash commits and create a pull request after feature implementation is complete. Only invoke when user explicitly requests to wrap up, create a PR, prepare for review, or finish the feature.
timsvoice
devops
git-workflows
0
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
JohnnyVicious
devops
git-workflows
0
context-read
Read and display project context from CLAUDE.md and all referenced [CONTEXT] commits for session initialization or review
KevinVitale
devops
git-workflows
0
cse247b-skill
Updates a user's overview.md and task markdown files in their respective project directory within the cse247b_reports_w26 repository. Use when the user mentions "overview" or "task".
Jazz23
devops
git-workflows
0
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
astrosteveo
devops
git-workflows
0
project-sync-checker
Check alignment between local project and git remote. Analyzes uncommitted changes, unpushed commits, unpulled updates, branch status, and divergence to ensure local and remote are synchronized.
jdeweedata
devops
git-workflows
0
jujutsu
MANDATORY skill for ALL version control operations. Load this skill BEFORE any VCS action. This project uses Jujutsu (jj) exclusively. Git commands are PROHIBITED. Always use jj commands for: commits, branching, rebasing, pushing, pulling, and all other VCS operations. MUST load when: (1) Creating or modifying commits, (2) Pushing to remote, (3) Creating branches or bookmarks, (4) Managing stacked diffs/PRs, (5) Resolving conflicts, (6) Any version control. Triggers: Any VCS operation, commits, branches, push, pull, rebase, stacked PRs, Change IDs.
kevinaud
devops
git-workflows
0
git-workflow
Guidelines for version control, commit conventions, and repository management.
ericbrian
devops
git-workflows
0
implement-feature
Checkout a new branch and implement a feature from a plan file. Use when the user says "/implement-feature {feature-file}" to start implementing a feature defined in plans/features/.
stevenraines
devops