Use Cases

Automatizando el flujo de trabajo de desarrollo completo con Claude Code

Ejemplos reales de automatización de tu flujo de trabajo de desarrollo desde la creación de Issue hasta la fusión de PR usando Claude Code.

Claude Code can automate not just one-off tasks but your entire development workflow. This article shows real examples for automating the path from issue creation to PR merge.

The Target Workflow

A typical development flow consists of these steps:

  1. Read an issue
  2. Create a branch
  3. Implement
  4. Write tests
  5. Open a PR
  6. Apply review feedback
  7. Merge

We’ll chain these together with Claude Code.

Step 1: From Issue to Implementation

Pass a GitHub issue number and Claude Code creates the branch, implements, and writes tests in one go.

#!/bin/bash
ISSUE_NUMBER=$1

claude -p "
Fetch GitHub Issue #${ISSUE_NUMBER} via the gh CLI and understand the content.
Then do the following:

1. Create branch issue/${ISSUE_NUMBER}-fix
2. Edit the necessary files to implement
3. Write tests (vitest)
4. Run npm test and ensure all tests pass
5. git add && git commit -m 'fix: #${ISSUE_NUMBER} ...'
"

./auto-fix.sh 123 is now all you need to fix issue #123.

Step 2: Automated PR Creation

Once implementation is done, let Claude Code create the PR too.

claude -p "
Use gh pr create to open the PR.
Auto-generate the title and body from the changes.

The body should include:
- Change summary
- List of modified files
- Test results
- Notes for reviewers

Finally open it with gh pr view --web.
"

A PR following your template is generated automatically.

Step 3: Self-Review Automation

Once the PR exists, run a self-review.

PR_NUMBER=$1
gh pr diff $PR_NUMBER | claude -p "
Review this PR for:
1. Possible bugs
2. Security risks
3. Performance concerns
4. Naming and readability
5. Test coverage

If issues exist, attach severity (high/medium/low) and post via gh pr review.
"

Self-reviews reduce the burden on human reviewers.

Step 4: CI/CD Integration

Combined with GitHub Actions, reviews run automatically on PR creation.

name: Claude Auto Review
on:
  pull_request:
    types: [opened, synchronize]

jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - name: Install Claude Code
        run: npm install -g @anthropic-ai/claude-code
      - name: Run review
        env:
          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          gh pr diff ${{ github.event.pull_request.number }} | \
            claude -p "Review this PR and flag any issues"

See Claude Code Hooks Guide for related setup.

Step 5: Post-Merge Cleanup

Cleanup of branches and related issues can be automated too.

claude -p "
PR #${PR_NUMBER} has been merged. Do the following:
1. Delete the local branch (git branch -d)
2. Delete the remote branch (git push origin --delete)
3. Close any related issues (gh issue close)
4. Append the merged content to CHANGELOG.md
"

Full Automation Script

Here’s auto-dev.sh that ties it all together.

#!/bin/bash
set -e

ISSUE=$1
if [ -z "$ISSUE" ]; then
  echo "Usage: ./auto-dev.sh <issue-number>"
  exit 1
fi

# 1. Create branch
git checkout -b "issue/${ISSUE}-fix"

# 2. Implement
claude -p "Implement Issue #${ISSUE} and write tests"

# 3. Run tests
npm test

# 4. Commit
git add -A
claude -p "Generate a git commit message from the changes and commit"

# 5. Push
git push -u origin HEAD

# 6. Open PR
claude -p "Open a PR via gh pr create"

# 7. Self-review
PR=$(gh pr view --json number -q .number)
gh pr diff $PR | claude -p "Self-review and flag any issues"

echo "✅ Automation complete! PR: $(gh pr view --web)"

Now ./auto-dev.sh 123 handles everything from branch creation to PR.

Caveats

1. Don’t over-automate

Auto-merging is dangerous. Always have a human review and let humans decide on merges.

2. Maintain test coverage

Auto-implemented code can only be verified by tests. Including auto-test generation, keep coverage above 80%.

3. Have a rollback path

You need to be able to roll back fast if something breaks. Keep commits small to make git revert easy.

Conclusion

  • Claude Code can automate from issue creation to PR merge
  • Combined with GitHub Actions, it integrates into a full CI/CD pipeline
  • Don’t over-automate; keep humans in the review/merge loop
  • Coverage and rollback paths give you safe operation

Combined with CI/CD Setup Guide and Subagent Patterns, you can build even more powerful workflows. See the Anthropic Claude Code docs for more.

#claude-code #automatización-flujo-trabajo #ci-cd #productividad

Lleva tu flujo con Claude Code al siguiente nivel

50 plantillas de prompts probadas en producción, listas para copiar y pegar en Claude Code.

Gratis

PDF gratuito: Hoja de trucos de Claude Code en 5 minutos

Solo deja tu correo y te enviaremos al instante la hoja de trucos en una página A4.

Cuidamos tus datos personales y nunca enviamos spam.

Masa

Sobre el autor

Masa

Ingeniero apasionado por Claude Code. Dirige claudecode-lab.com, un medio tecnológico en 10 idiomas con más de 2.000 páginas.