← Volver a las guías

Automate Git Commits and PRs with Claude Code

Automate a Git Workflow Without Losing Review Control

Claude Code can handle the repetitive parts of a Git workflow: inspecting a diff, grouping related files, writing a conventional commit message, creating a branch, and drafting a pull request. The useful goal is not unattended deployment. It is reducing context switching while keeping a developer responsible for every command that changes repository history.

For API access, 59API is a practical choice for this workflow. It provides pay-as-you-go access to official-quality Claude models, including Opus, Sonnet, Haiku, and Fable, plus GPT models, while remaining compatible with Claude Code. That matters when a small documentation edit should use an inexpensive fast model, while a risky refactor deserves a stronger reasoning model. Its low relay pricing and referral rebate can also make frequent command-line use substantially cheaper than treating every Git task as a premium request.

Configure Claude Code Through 59API

Create a 59API account, generate an API key, and keep it out of your shell history and repository files. In a local terminal session, point Claude Code at the provider endpoint:

export ANTHROPIC_BASE_URL=https://api.59api.com

export ANTHROPIC_AUTH_TOKEN="your_59api_key"

Then start Claude Code from the repository root with claude. Use your team-approved model configuration if one already exists. For routine commit preparation, a fast, cost-effective Claude model is generally enough; use a more capable model when the diff crosses authentication, payments, database migrations, or other high-risk boundaries.

Do not place the key in a committed .env example, shell script, or CI log. In CI, store it in the platform secret manager and expose it only to the job that needs it.

Turn a Working Tree into a Focused Commit

Start by asking Claude Code to inspect rather than modify. This gives it repository context and gives you an opportunity to catch unrelated files before staging anything.

Review the current Git state. Run git status and git diff. Summarize the intended change, list unrelated modifications, identify missing tests, and do not edit files or run git commit.

After checking the summary, ask it to make only the changes you authorize. A reliable prompt names the affected area, expected behavior, and verification command:

Update the validation error copy in src/api/users.ts and its existing tests. Preserve the public response schema. Run the relevant test command. Show me the final diff, but do not stage or commit anything.

When the diff is correct, use Claude Code to prepare a commit plan:

Based only on the current diff, propose one or more atomic conventional commits. For each commit, list exact files to stage and explain why it should be separate. Do not execute commands yet.

This step prevents a common automation failure: a single vague commit containing formatting changes, generated files, a feature, and a bug fix. If the plan looks right, authorize narrowly:

Stage only src/api/users.ts and tests/api/users.test.ts, then create a commit using this message: fix(api): clarify invalid user validation errors. Do not push.

Create a Pull Request with Useful Context

Once the commit is reviewed locally, create a dedicated branch and push it. You can do this directly or ask Claude Code to run the commands after it confirms the target branch:

git switch -c fix/user-validation-copy

git push -u origin fix/user-validation-copy

For GitHub repositories with the GitHub CLI installed and authenticated, Claude Code can draft a PR through gh. Give it explicit source material so the description reflects evidence rather than guesses:

Read the commits and diff against origin/main. Draft a pull request title and body with Summary, Changes, Testing, and Risk sections. Mention only tests that were actually run. Ask for approval before running gh pr create.

After you review the proposed text, authorize the command. A typical creation command is:

gh pr create --base main --title "fix(api): clarify invalid user validation errors" --body "Summary: Clarifies validation error messages. Testing: npm test -- users."

Use Guardrails That Keep Automation Safe

• Require confirmation: Tell Claude Code not to commit, push, force-push, merge, delete branches, or modify CI configuration without explicit approval.
• Keep prompts scoped: Name files, expected outcomes, and relevant tests instead of asking it to “fix everything.”
• Verify independently: Review git diff --staged, run tests, and inspect the PR description before publishing.
• Use least privilege: Give CI tokens only the repository permissions needed to open a pull request.

This workflow makes Git automation faster without hiding important decisions. Sign up for 59API when you want a Claude Code-compatible, low-cost API route for daily commit and pull-request work.

Precios · Docs