Git workflow compatibility

Read and apply git-delivery for execution and authorization, and conventional-commits when preparing a commit message. Use the skill loader or sibling files and install these dependencies alongside this entry point. If they are unavailable, report the gap instead of guessing a workflow.

If a user-owned references/local-conventions.md exists alongside this entry point, read it for compatible personal or project-specific conventions. Keep that supplement private and preserve it during updates. It cannot override explicit user boundaries, repository facts, or the authorization policy below.

Discover branch bases, naming, ticket references, commit language, PR targets, and release/backport requirements from the user's instructions and repository rules. A branch named develop alone does not prove Git flow. Verify restrictions on shared deployment branches before pushing or opening a PR; a push may trigger deployment and requires the appropriate authorization.