By gupsammy
Automate Git-powered coding workflows: generate atomic conventional commits from changes, push to feature branches and create/update PRs, clean merged/stale branches, fetch organized PR comments, generate/update READMEs and changelogs, maintain CLAUDE.md docs, and set up GitHub Actions for Claude Code—all with AI agents for audits.
npx claudepluginhub gupsammy/claudest --plugin claude-codingUse this agent when you need architectural guidance or review. Recommended PROACTIVELY after adding features that span 3+ modules, refactoring cross-module boundaries, or making structural design decisions. Not for naming, formatting, or single-file style questions — those are code quality, not architecture.
Use this agent when you need code quality review — readability, correctness, dead code, naming, and consistency. Use PROACTIVELY after implementing features, fixing bugs, or refactoring. Focuses on changed code and its immediate context. Not for security (use security-auditor), performance (use performance-auditor), or architectural patterns (use architecture-auditor).
This skill should be used when the user says "clean up branches", "delete merged branches", "prune stale branches", "git branch cleanup", "remove old branches", or wants to tidy up or purge old branches.
This skill should be used when the user says "commit my changes", "commit this", "create a commit", "git commit", "save my work", or mentions committing code.
This skill should be used when the user says "get PR comments", "show PR feedback", "what comments on my PR", "PR review comments", "show me the review", "what did reviewers say", or asks about feedback on a pull request. Not for creating PRs or responding to comments.
This skill should be used when the user asks to "create a changelog", "generate a changelog", "update my changelog", "fill in the changelog", "add a changelog", "CHANGELOG is missing entries", "changelog is out of date", "what's missing from my changelog", "changelog from git history", "write changelog", "release notes", or says "my project needs a CHANGELOG".
This skill should be used when the user asks to "create a README", "generate a README", "make a readme", "write a README for my project", "need a README", "add a README", "document my project", "set up project docs", "readme with badges".
This skill should be used when the user wants to create a pull request, or submit code for review. Triggers on "push a PR", "create a PR", "open a pull request", "make a PR", "submit for review".
This skill should be used when the user asks to update, refresh, optimize, or clean up CLAUDE.md, or when documentation is stale, verbose, or out of sync with codebase reality. Triggers on "update CLAUDE.md", "refresh the docs", "sync CLAUDE.md with the codebase", "optimize project instructions", "clean up CLAUDE.md", "improve CLAUDE.md", "fix CLAUDE.md".
This skill should be used when the user asks to "update my README", "refresh the README", "README is outdated", "sync README with the codebase", "improve my README", "keep README up to date", "fix the README", "my README is stale", "update the readme file", "README needs updating", "update readme from git history", or "readme is out of date".
Streamline your git workflow with simple commands for committing, pushing, and creating pull requests
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Editorial "OSS Maintainer" bundle for Claude Code from Antigravity Awesome Skills.
GitHub and Git workflow tools: commit-creator, pr-creator, pr-reviewer, and pr-comment-resolver agents, slash commands for commits, PRs, and review comment resolution, plus skills for PR/commit workflows.
Enforce conventional commits, conventional comments, and engineering ownership for commits, PRs, and code reviews
Commands for Git operations, commits, and PRs
Intelligent git commits with conventional format, semantic analysis, and changelog generation