hs:git

Stage your changes and invoke the commit operation, which analyzes the staged diff and generates messages in the type(scope): description format. When changes span multiple types, it splits them into separate atomic commits for config, dependencies, tests, code, and docs.

The skill runs a mandatory grep-based scan of the staged diff for patterns like API keys, AWS AKIA identifiers, tokens, passwords, private keys, and database connection strings. If any match is found, the commit is blocked until you remove the secret or move it to environment variables.

Yes, the merge-pr operation wraps gh pr merge and defaults to squash-merging the current branch's open PR with branch deletion. It refuses to proceed when checks are failing or the PR has conflicts, and watches target-branch CI after the merge completes.

The pre-push hook requires a verification.json artifact and calls artifact_check.check_stage before allowing any push. If the artifact is missing or python3 is unavailable, the hook exits with a fail-closed error; create the verification artifact as instructed rather than bypassing the hook.

Never force push to main, master, production, or release branches; the skill warns and refuses in those cases. Force pushing a feature branch is allowed only after explicit user confirmation, since it rewrites history and can cause collaborators to lose work.