From git-workflows
Always-on branch safety rules: never commit or push directly to main/master, create feature branches with rh/ prefix
npx claudepluginhub remihuguet/rems-buddy --plugin git-workflowsThis skill uses the workspace's default tool permissions.
Before any commit or push operation, check the current branch. If on `main` or `master`, create a new feature branch first.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Provides patterns for autonomous Claude Code loops: sequential pipelines, agentic REPLs, PR cycles, de-sloppify cleanups, and RFC-driven multi-agent DAGs. For continuous dev workflows without intervention.
Applies NestJS patterns for modules, controllers, providers, DTO validation, guards, interceptors, config, and production TypeScript backends with project structure and bootstrap examples.
Before any commit or push operation, check the current branch. If on main or master, create a new feature branch first.
# Good
git switch -c rh/add-user-auth
git commit -m "feat(auth): add user authentication"
# Bad
git commit -m "feat(auth): add user authentication" # while on main
git push origin main # pushing directly to main
rh/ prefix for new branch namesWhen creating a branch, use the rh/ prefix followed by a short, descriptive kebab-case name.
# Good
rh/add-user-auth
rh/fix-login-redirect
rh/refactor-api-client
# Bad
feature/add-user-auth
add-user-auth
my-branch
If unsure whether to create a new branch or which name to use, ask the user before proceeding. Suggest a default name based on the changes with rh/ prefix.