Developer Tools & Repos Agent Skills for Claude Code

Use when configuring Ghostty terminal emulator, working with ghostty config files, or looking up Ghostty settings and options.

When to activate: Gin web framework, routing groups, middleware, request binding, validation, error handling, Gin context

Working with git and GitHub as an agent using a dedicated account (e.g. "yrodiere-agent").

Generates context-aware, Conventional Commits-compliant Git commit messages and safely commits task changes.

Enforces team git branching, commit messaging, and pull request conventions aligned with Jira workflow standards.

Generate high-quality conventional git commit messages and, with user approval, run the commit.

Enforces Conventional Commits 1.0.0 standards and structured version control workflows across polyglot projects.

Apply Singleton SD git conventions — commit format, branch naming, ticket linking, and sibling worktrees

Enforces disciplined Git workflows, atomic Conventional Commits, branch hygiene, and Pull Request lifecycles.

Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code…

Use for any git operation (commit, push, pull, rebase, branch, PR, cherry-pick, etc.).

Cleans up merged Git branches, removes associated worktrees safely with explicit approval, and updates the main branch.

Git identity and GPG signing profile manager.

Diagnoses and safely fixes bugs in Git repositories using isolated worktrees with strict code review and testing validation.

Clones specified Git repositories and branches safely into designated workspace directories without overwriting existing code.

Complete guide to installing Git and performing basic configuration across all platforms (Windows, macOS, Linux, WSL).

Git operations including worktrees, branching, and repository management

Stage selected git hunks non-interactively by reusing the source workflow under `claude/git-stage-hunk`.

Use when planning git branching strategies or managing branches for development.

Use when writing commit messages that clearly communicate changes and tell the story of development.

Use when planning commit strategies or determining when to commit changes.