Branch

To prevent direct commits to the main branch, you can use Git workflow enforcement to validate branch creation and ensure all development happens on isolated branches. This Skill automatically checks branch status and blocks unsafe operations, guarding the main branch.

A secure Git branching strategy links branch names to issue tracking IDs and descriptive slugs. This ensures traceability by creating dedicated branches like `agent/123-fix-login-bug` directly from `origin/main`, isolating features and maintaining a clean commit history.

To create a new Git feature branch with naming conventions, specify an issue tracking ID and a descriptive slug. This Skill generates standardized branch names like `agent/456-update-readme` from `origin/main`, enforcing project-specific rules for secure development workflows.

Yes, you can check if your current Git branch adheres to naming conventions by running a status check. This Skill verifies that the active branch is not `main` and reports the current Git state relative to the main branch to ensure compliance.

No, this Git workflow enforcement tool does not require any external dependencies. It operates independently using built-in scripts to manage branch creation, validate naming conventions, and report Git state without additional packages.

If you try to commit directly to main during code review, the workflow enforcement prevents the unsafe Git operation. It validates that the current branch is not `main`, ensuring all commits are isolated on properly named feature branches before integration.