Git i control de versions
Operacions de Git, assistència per a commits i gestió de branques
analyze-answers
bdmorin
You are a PHD expert on the subject defined in the input section provided below.
asncli
michalvavra
CLI for Asana. Manage projects and tasks.
analyze-interviewer-techniques
bdmorin
Fabric pattern: analyze_interviewer_techniques
promptscript
mrwogu
PromptScript language expert for reading, writing, modifying, and troubleshooting .prs files. Use when working with PromptScript syntax, creating or editing .prs files, adding blocks like @identity, @standards, @restrictions, @shortcuts, @skills, or @agents, configuring promptscript.yaml, resolving compilation errors, understanding inheritance (@inherit) and composition (@use, @extend), or migrating AI instructions to PromptScript. Also use when asked about compilation targets (GitHub Copilot, Claude Code, Cursor, Antigravity, Factory AI).
write-conventional-commit
ragnarok22
Create Git commit messages that conform to Conventional Commits 1.0.0, including type/scope/description format, optional body, trailer-style footers, and explicit BREAKING CHANGE signaling. Use when users ask to draft commit messages, commit current changes, rewrite a commit message into conventional format, or enforce conventional commit standards in a repo.
release
intrusive-memory
Release a merged PR by tagging and creating a GitHub release. Use when asked to "release", "tag", or "create a release".
ship-swift-library
intrusive-memory
Ship and release Swift library versions by bumping the version on development, merging the PR once CI passes, then tagging and creating a GitHub release from main
approve_issue
EdanStarfire
Approve completed issue work, merge PR, and clean up resources
upkeep-audit
wei18
Run the Upkeep repo audit locally against any repository path. Use when asked to audit a repo, check docs/spec/asset drift, or run upkeep without GitHub Actions.
git-sync
EdanStarfire
Synchronize local default branch with remote, ensuring up-to-date base for worktrees.
plan_issue
EdanStarfire
Start planning phase for an issue by spawning a Planner minion
github-pr-manager
EdanStarfire
Create, view, and merge GitHub pull requests with validation. Use when creating PRs from branches, checking PR status, or merging approved PRs with cleanup.
worktree-manager
EdanStarfire
Manage git worktrees for isolated issue work. Create, list, and remove worktrees safely.
status_workers
EdanStarfire
Show status of all active issue workers and their progress
git-branch-manager
EdanStarfire
Create, switch, and manage git branches with proper handling of uncommitted changes. Use when creating feature branches, switching contexts, or cleaning up after merges.
Git Workflow Standards
hivellm
CLI tool to standardize AI-generated projects with templates, rules enforcement, and automation
Dotfiles Best Practices
kriscard
"Dotfiles: Reference knowledge for modern CLI tools and shell best practices. Loaded by dotfiles-optimizer when needed."
git-workflow
samhvw8
"Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes."
sequential-thinking
samhvw8
"Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems."
git-workflow
salavender
Standardized patterns for Git branching, worktrees, and lifecycle management.
session-resume
salavender
Resume context from previous session
run-control-tower
AlexanderMattTurner
How to run the external Control Tower / LinuxArena eval (glovebox's marginal-defense benchmark) — dispatching the live Kata-microVM e2e, building the cells JSON, picking the agent model + budget, and pulling the .eval transcripts back. Activate whenever the user asks to "run CT", "run the Control Tower eval", "smoke test the CT harness / all CT environments", "run a guarded-condition eval", "dispatch the CT e2e suite", "measure marginal defense / ΔS / ΔU", or wants to scan CT eval transcripts. Covers dispatch mechanics; the honesty rules live in .claude/rules/control-tower-eval.md and load with the CT tree.
git-workflow
AlexanderMattTurner
The mechanics of committing, pushing, and resolving merge conflicts in this repo. Activate before you commit or push, when a PR reports a merge conflict or a dirty mergeable_state, when a merge-conflict label or an auto-resolve bot comment arrives, when you must audit a bot's merge resolution or answer a merge-delta finding thread, when you are about to push work that belongs to an already-open PR, and when you are tempted to re-run the suite locally after a push. The load-bearing rule is that a conflict belongs to the auto-resolve workflow, not to you.
pr-creation
AlexanderMattTurner
Creates high-quality pull requests with an iterative compress-critique-fix loop before submission. Activate this skill whenever you are asked to create, open, submit, or push a pull request, OR whenever a new feature, fix, or refactor is complete and ready to ship. Also activate when the user says "make a PR", "open a PR", "submit this for review", "push and create a PR", "I'm done, create the PR", "the feature is done", "I'm finished", or any variation of completing work / requesting a pull request. Also activate to update, fix, or add to an existing PR — "update the PR", "fix the PR", "add this to the PR" (see "Updating an existing PR"). Always activate before opening or editing a PR, whatever the route — CLI or API tool.