git-workflows
5
spec-update
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
CongDon1207
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
git-workflows
5
merge-request
Working with GitLab merge requests via glab. Use when creating, updating, reviewing, or merging MRs.
bendrucker
devops
git-workflows
5
squash-branch
Squash all commits on a feature branch into a single commit. Use when the user wants to clean up commit history, squash commits, or consolidate branch changes into one commit.
josehu07
devops
git-workflows
5
session-start
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
troykelly
devops
git-workflows
5
using-github-cli-gh
Master GitHub CLI workflow for issues, repos, search, and APIs. Use when creating/reading GitHub issues, searching repos, querying GitHub data, or automating GitHub tasks. Focus: gotchas, key workflows with "look at past examples" pattern, practical APIs.
WarrenZhu050413
devops
git-workflows
5
rust-best-practices-guide
A comprehensive guide to modern Rust best practices covering style, error handling, performance, concurrency, project organization, dependency management, documentation, testing, security, and CI.
mosif16
devops
git-workflows
5
gerrit-comment
Fetch and post Gerrit review comments (as JSON) for a given change URL, change number, or Change-Id. Use when you need real review feedback for code fixes or want to post automated review comments.
XuNeo
devops
git-workflows
5
git-advanced-workflows
rebase、cherry-pick、bisect、worktree、reflogを含む高度なGitワークフローをマスターし、クリーンな履歴を維持し、あらゆる状況から回復。複雑なGit履歴の管理、フィーチャーブランチでの協働、リポジトリ問題のトラブルシューティング時に使用。
amurata
devops
git-workflows
5
save-workflow-state
Save conductor workflow state to JSON file for smart resumption, tracking current phase, completed phases, issue context, and branch information
BerryKuipers
devops
git-workflows
5
branch-discipline
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
troykelly
devops
git-workflows
5
commit-lint
Validate commit messages against conventional commit format
shunkakinoki
devops
git-workflows
5
github-navigator
GitHub operations via gh CLI. CRITICAL: Always use instead of WebFetch for ANY github.com URL. Use when user provides GitHub URL, says 'facebook/react', 'show README', 'list issues', 'check PR', 'clone repo', 'analyze this repo', 'understand the architecture', 'how is X structured', 'explore the codebase'. For deep analysis of external repos, clones locally.
arvindand
devops
git-workflows
5
tasks-spec-update
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
CongDon1207
devops
git-workflows
5
conventional-commits
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
clawdbot
devops
git-workflows
5
code-review
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
CongDon1207
devops
git-workflows
5
worker-dispatch
Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel execution and TaskOutput for monitoring. Pre-extracts context to minimize worker token usage.
troykelly
devops
git-workflows
5
pr-process
Prepare commits and pull requests for this repo following the PR template and Conventional Commits.
proompteng
devops
git-workflows
5
comprehensive-review
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
troykelly
devops
git-workflows
5
add-app-config
Use when adding configuration for a new application to the dotfiles, setting up a new tool's config, or when user says "add config for X"
avegancafe
devops
git-workflows
4
ghe-claim
CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree. USE THIS SKILL WHEN: - User says "claim issue #N" or "claim #N" - User says "start working on issue #N" or "take issue #N" - User says "I'll work on #N" or "pick up #N" - User wants to BEGIN work on a specific issue number - User selected an issue from available work and wants to claim it REQUIRED: An issue number must be specified or identifiable from context. DO NOT USE THIS SKILL WHEN: - User just wants to SEE status (use ghe-status) - User is ALREADY working and wants to post update (use ghe-checkpoint) - User wants to CHANGE phases (use ghe-transition) - User wants reports (use ghe-report) - No specific issue number is mentioned EXAMPLES: <example> Context: User wants to start work on a specific issue user: "Claim issue #201" assistant: "I'll use ghe-claim to claim issue #201 with the full protocol" </example> <example> Context: User picks from
Emasoft
devops
git-workflows
4
ghe-status
READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance. USE THIS SKILL WHEN: - User asks "what's the status" or "show me the status" - User asks "what threads are active" or "what am I working on" - User asks "show me the workflow state" or "what's happening" - User wants a quick overview before starting work - Starting a session and need context DO NOT USE THIS SKILL WHEN: - User wants to CLAIM an issue (use ghe-claim) - User wants to POST a checkpoint (use ghe-checkpoint) - User wants to TRANSITION phases (use ghe-transition) - User wants DETAILED metrics/health reports (use ghe-report) EXAMPLES: <example> Context: User starting a session wants to see current state user: "What's the github elements status?" assistant: "I'll use ghe-status to show you the current workflow state" </example> <example> Context: User wants to know what work is available user: "Show me what threads are active" assistant: "I'll use ghe-status to disp
Emasoft
devops
git-workflows
4
sharex-workflow-and-versioning
Semantic versioning, commit message standards, multi-agent coordination, and workflow guidelines
ShareX
devops