By remihuguet
Conventional commit and push workflows with always-on commit conventions
Rem's buddy — reusable Claude Code skills packaged as a plugin marketplace. Install once, use across all projects.
Add to your Claude Code plugins:
/plugins add /Users/remihuguet/workspaces/rems-buddy
Or add to .claude/settings.json:
{
"plugins": ["/Users/remihuguet/workspaces/rems-buddy"]
}
Strict red-green workflow: write a failing test reproducing the bug, implement minimal fix, run full suite, commit.
/bugfix users can log in with expired tokens
Commands: /commit, /commit-push
Always-on skill: conventional commit message formatting rules.
Always-on guidance for domain naming, intent-revealing identifiers, comment strategies, and minimal docstrings.
Three skills providing always-on guidance:
Six skills for Python backend architecture:
Always-on prompt interpretation: resolve ambiguity from context, decompose vague requests, minimize unnecessary questions.
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest (name, description, version, author)
├── commands/ # On-demand slash commands
│ └── my-command.md
├── skills/ # Always-on behavioral guidance
│ └── my-skill/
│ └── SKILL.md
└── README.md
.claude-plugin/plugin.json with name, description, version, and authorskills/<skill-name>/SKILL.mdcommands/<command-name>.md with YAML frontmatter.claude-plugin/marketplace.jsonmarketplace.json are relative to the plugin source (e.g., ./skills/my-skill)Runs pre-commands
Contains inline bash commands via ! syntax
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.
npx claudepluginhub remihuguet/rems-buddy --plugin git-workflowsTDD bug fix workflow: reproduce with failing test, fix, verify, commit
Coding conventions for self-documenting code: naming, comments, docstrings
Python backend architecture: hexagonal layers, DDD, CQRS, event-driven patterns
Always-on prompt interpretation: resolve ambiguity from context, decompose vague requests, minimize unnecessary questions
Python testing conventions, philosophy, and organization with pytest
Git commit workflow: atomic commits, validation, conventions
Streamline your git workflow with simple commands for committing, pushing, and creating pull requests
Git workflow automation: conventional commits with branch protection, ticket tracking, and semantic correlation
Streamline your git workflow with simple commands for committing, pushing, and creating pull requests
Creates git commits using conventional commit format with appropriate emojis, following project standards and creating descriptive messages that explain the purpose of changes.
When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.