feat: add protected-branch check to git safety rules

[euxaristia]

Summary

• Add a rule to check for protected branches before pushing, and open a PR instead when protected.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates CLAUDE.md to include a guideline for checking branch protection before pushing. Feedback suggests using a more reliable GitHub API endpoint and query to determine protection status, as the previously suggested endpoint returns a 404 error for unprotected branches.

[euxaristia]

/gemini review

[gemini-code-assist]

Code Review

This pull request updates CLAUDE.md to include a guideline for checking branch protection before pushing. A suggestion was made to use :owner and :repo placeholders in the gh api command to leverage the CLI's automatic context resolution.

[gemini-code-assist]

Use :owner and :repo placeholders in the gh api example. The gh CLI automatically resolves these to the current repository's context, simplifying execution for the AI.

Suggested change

	- Before pushing, check whether the target branch is protected (e.g. `gh api repos/{owner}/{repo}/branches/{branch} -q .protected`); if protected, create a feature branch and open a PR instead of pushing directly
	- Before pushing, check whether the target branch is protected (e.g. `gh api repos/:owner/:repo/branches/{branch} -q .protected`); if protected, create a feature branch and open a PR instead of pushing directly

References

1. The user prefers extremely concise and brief responses. Prioritize high signal-to-noise ratio and minimal conversational filler. ^(link)