From devloop
Guides git workflows: branching strategies, conventional commits, PR processes, release management, trunk-based development, git flow, and merge strategies.
npx claudepluginhub zate/cc-plugins --plugin devloopThis skill uses the workspace's default tool permissions.
Best practices for git branching and collaboration.
Recommends Git branching strategies (trunk-based, GitHub Flow, Git Flow, GitLab Flow), commit conventions, PR workflows, release management, monorepos, semantic versioning, and protected branch policies for teams.
Guides Git workflow strategies like GitFlow, GitHub Flow, Trunk-Based Development for team collaboration, branch setup, merge strategies, and best practices.
Provides Git workflow guidance on branching strategies (GitHub Flow, Trunk-Based, GitFlow), conventional commits, merge vs rebase, conflict resolution, and team best practices. Activate for project setup, PRs, releases, onboarding.
Share bugs, ideas, or general feedback.
Best practices for git branching and collaboration.
Configure git workflow in .devloop/local.md:
---
git:
auto-branch: true # Create branch when plan starts
branch-pattern: "feat/{slug}"
pr-on-complete: ask # ask | always | never
---
Related commands:
/devloop:ship - Commit with plan context, create PR/devloop:pr-feedback - Integrate review comments<type>/<ticket>-<description>
feat/AUTH-123-add-oauth
fix/BUG-456-null-pointer
feat/add-authentication (devloop default)
Modern approach favored by high-performing teams:
Devloop fit: Plan → Branch → Implement → Ship → PR
<type>(<scope>): <description>
feat(auth): add OAuth2 login support
fix(api): handle null response
refactor(utils): extract date formatting
| Type | Description |
|---|---|
| feat | New feature (MINOR) |
| fix | Bug fix (PATCH) |
| docs | Documentation |
| refactor | Code restructure |
| test | Tests |
| chore | Maintenance |
Devloop auto-generates commit messages from plan tasks using conventional format.
/devloop:ship when ready/devloop:pr-feedbackNever on shared branches: