git-workflows
0
github-pull-requests
Create a GitHub pull request with conventional commit title
dtu-mlops
devops
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
git-workflows
0
conventional-commits
Conventional Commits specification format. Use when creating commit messages. Format: <type>(<scope>): <description>. Types: feat, fix, chore, docs, test, refactor, style, perf. CRITICAL: All commits must follow conventional commit format.
GolferGeek
devops
git-workflows
0
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.
untangledfinance
devops
git-workflows
0
git-worktree-guide
Git worktree management with the `wt` script for simplified create, list, switch, and delete operations. Includes comprehensive guidance on best practices and troubleshooting.
trounceabout
devops
git-workflows
0
github-triage
Use the GitHub CLI (gh) to find and summarize relevant GitHub issues/PRs from an error message or keywords, preferring exact-phrase searches scoped to a repo and returning issue/PR numbers + URLs.
Altinity
devops
git-workflows
0
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
donellmccoy
devops
git-workflows
0
safe-commit
Safely create git commits with an agent tag prefix (e.g. [ANTIGRAVITY], [CODEX], [CLAUDE]), security validation, and proper user config. Use when committing code changes, creating commits, or when user says "commit", "save changes", or "git commit".
junsuwhy
devops
git-workflows
0
cartographer
Tools to maintain the repository map. Use ONLY when the project structure has changed significantly.
FrostadEng
devops
git-workflows
0
sdd-skill-creator
Generate project-specific SDD skills for a repository. Use when: setting up SDD for a new project, customizing SDD for a domain, creating repo-local skills that implement `doc/sdd-guidelines.md`. Triggers: "create sdd skills", "setup sdd for project", "customize sdd"
h2b-dev-studio
devops
git-workflows
0
git-conventions
Git 操作の共通規則とベストプラクティス。安全規則、機密ファイル、禁止事項を定義。全ての Git 操作で自動適用される。
biwakonbu
devops
git-workflows
0
agentuity-cli-git-unlink
Unlink a project from its GitHub repository. Requires authentication
agentuity
devops
git-workflows
0
beads-session-sync
Flush and sync Beads changes to git (export/commit/pull/import/push)
dikini
devops
git-workflows
0
session-wrapup
Complete end-of-session workflow for SheldonFS project. Handles code commits, quality checks, documentation updates, and merge process. Use when finishing a development session or feature branch.
Hameem1
devops
git-workflows
0
leavn-commit-machine
Create clean, descriptive git commits for Leavn app following emoji prefix convention with comprehensive change summaries
willsigmon
devops
git-workflows
0
global-conventions
Follow project-wide development conventions including consistent project structure, clear documentation, version control best practices, environment configuration, dependency management, code review processes, and modular architecture following Open/Closed Principle. Use this skill when organizing project files and directories, writing README files, creating commit messages, managing dependencies, setting up environment variables, implementing feature flags, or designing modular system boundaries. Use when working with configuration files (.env, package.json, requirements.txt, Cargo.toml), documentation files (README.md, CONTRIBUTING.md), version control operations, or architectural decisions about how to structure and organize code across the entire project.
maksimtereshin
devops
git-workflows
0
forensic-change-coupling
Use when planning architecture refactoring, understanding cross-module dependencies, discovering hidden dependencies, finding shotgun surgery patterns, or identifying files that change together - reveals temporal coupling and architectural violations using git history analysis
AlabamaMike
devops
