gitSafety 90Repository ShareFavorite skill

<essential_principles>

<git_safety> Never run without explicit user request:

• git push --force to main/master
• git reset --hard
• --no-verify flag (skip hooks)
• git commit --amend on pushed commits
• Direct push to main/master (create feature branch first)

Always verify before acting:

• git status before staging
• git log --oneline -5 for commit style
• Check remote tracking before push

Branch naming:

• Features: feat/description
• Fixes: fix/description
• Chores: chore/description </git_safety>

<commit_format> Commit message structure:

type(scope): short description

- What changed (if not obvious from description)
- Why it changed (motivation)

Co-Authored-By: Claude <noreply@anthropic.com>

Types: feat, fix, refactor, test, docs, chore, perf

Use HEREDOC for multi-line messages:

git commit -m "$(cat <<'EOF'
feat(auth): add JWT refresh token rotation

- Rotates refresh tokens on every use
- Prevents replay attacks on stolen tokens

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

</commit_format>

<pr_format> PR body:

## Summary
- [What this PR does in 1-3 bullets]

## Test plan
- [ ] [Test 1]
- [ ] [Test 2]

## Changes
- [File 1]: [What changed]
- [File 2]: [What changed]

</pr_format>

</essential_principles>

1. Commit — Stage and commit changes
2. Push — Push commits to remote
3. PR — Open a pull request
4. Ship — Full workflow: commit + push + PR

Wait for response.

<workflows_index>