Git Commit PR Workflow

This skill appears to be what it says (end-to-end git -> PR), but it omits operational details you should confirm before using it: - Verify the agent environment actually has git and any CLI tools it will use (git, gh, hub) and that those are the intended tools. The skill itself does not declare these as requirements. - Confirm how authentication will be performed: will it rely on SSH keys present in the environment, an existing remote credential, or an API token? If API tokens or SSH keys are available to the agent, ensure they have only the minimum needed permissions and do not expose sensitive repos. - Ask the skill author to document which remote host (GitHub/GitLab/other) the skill targets and whether it will call a third-party API or use the local git client. Lack of this detail can lead the agent to push or open PRs in unexpected locations. - Because instructions are high-level and allow broad discretion, review the exact git commands the agent plans to run before allowing execution — especially any operation that could rewrite history or touch protected branches. - Test the skill first in a non-sensitive repository or fork, and restrict its use to user-invoked runs rather than automatic/always-on invocation. If you need the skill, request the maintainer add explicit requirements (git binary, preferred CLI/tooling, and documented auth mechanism) so you can validate them before granting the agent access to real repositories.