By timo-jakob
General development workflow skills for committing, branch naming, and other git operations.
Cleans up the local git environment after merging a branch to main. Prunes stale remote-tracking branches and deletes local branches that are already merged into main. Run this after a PR is merged to main.
Commit code changes after running formatting/linting and generating a commit message
Defines how git branches must be named at this organization. Use this skill whenever Claude Code is about to create a git branch, suggest a branch name, check out a new branch, or when the user asks "what should I name this branch", "create a branch for...", or "start work on issue #...". Always consult this skill before proposing or creating any branch name — even for quick fixes or experiments.
Fetch current documentation for any library or framework before using it. Use whenever writing, reviewing, or explaining code that involves an external library or framework — especially when the correct API, method signatures, or version-specific behaviour matters.
Executes bash commands
Hook triggers when Bash tool is used
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A collection of plugins for Claude Code.
Language-agnostic workflow tooling for git operations, committing, and branch management.
Skills:
| Skill | Command | Description |
|---|---|---|
| Commit | /development:commit [message] | Runs formatting/linting (delegates to language-specific plugin), generates a commit message, ensures a feature branch, and commits |
| Git Branch Naming | /development:git-branch-naming | Defines the branch naming convention (<type>/<issue>-<description>) and creates properly named branches |
Agents:
| Agent | Model | Focus |
|---|---|---|
| Commit Message | sonnet | Generates clear commit messages from diffs, ignoring formatting/linting noise |
Swift-specific development tooling — code review and formatting/linting.
Skills:
| Skill | Command | Description |
|---|---|---|
| Review | /dev-swift:review [paths] | Spawns 6 specialized agents in parallel to analyze bugs, security, performance, Swift 6 compliance, code quality, and test coverage |
Agents:
| Agent | Model | Focus |
|---|---|---|
| Bug Hunter | opus | Logic errors, nil crashes, race conditions, stability |
| Security Reviewer | sonnet | Secrets, injection, insecure storage, ATS, keychain |
| Performance Reviewer | sonnet | Retain cycles, allocations, O(n²), main thread blocking |
| Swift 6 Compliance | sonnet | Strict concurrency, typed throws, modern syntax |
| Code Quality | sonnet | Naming, SOLID, readability, dead code, API design |
| Test Reviewer | sonnet | Coverage gaps, assertion quality, flaky tests |
| Swift Lint & Format | sonnet | Runs SwiftFormat and SwiftLint, fixes issues in-place |
Load plugins locally during development:
claude --plugin-dir ./development --plugin-dir ./dev-swift
Then use the slash commands:
# Development workflow
/development:commit # format, lint, generate message, commit
/development:commit "Fix auth" # format, lint, commit with given message
# Swift code review
/dev-swift:review # review all Swift files
/dev-swift:review Sources/ # review a specific directory
MIT
npx claudepluginhub timo-jakob/timos-claude-code-plugins --plugin developmentStreamline your git workflow with simple commands for committing, pushing, and creating pull requests
Streamline your git workflow with simple commands for committing, pushing, and creating pull requests
Commands for Git operations, commits, and PRs
Git commit workflow: atomic commits, validation, conventions
Automates git commit process by selecting the first suggested message, generating structured commits with consistent formatting while skipping manual confirmation and removing Claude co-Contributorship footer
Git storytelling guidance - helps commit work thoughtfully to tell the story of your development process.