Files

Paul O'Reilly a4967df815 Initial commit: Claude Code foundations and improvements research

Conventions, community best practices research (Sept 2025 - March 2026),
and prioritized improvement backlog for Claude Code workflows.

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

2026-03-12 23:02:54 +13:00

1.6 KiB

Raw Blame History

CI/CD Integration

Why This Matters

60%+ of teams adopting Claude Code now use headless mode (claude -p) for automation. The most productive pattern is interactive Claude for architecture/design while delegating routine reviews and migrations to headless CI.

Current State

No CI/CD integration with Claude Code
Projects hosted on Gitea (not GitHub, so GitHub Actions patterns need adaptation)

Patterns

Headless Mode (`claude -p`)

Run Claude non-interactively in scripts or CI pipelines:

claude -p "Generate changelog from recent commits" --output-format json
claude -p "Review this diff for security issues" < diff.txt
Useful for automated PR review, changelog generation, migration scripts

Automated PR Review

Claude reviews PRs automatically on open/update (15-45 seconds per review). Would need a Gitea webhook + runner setup rather than GitHub Actions.

Cross-Model Validation

Advanced pattern: global CLAUDE.md tells Claude to send diffs to Gemini/Codex for independent validation before committing. "High catch rate" reported by users.

Compounding Engineering

Autonomous CI where Claude handles routine tasks (dependency updates, code style fixes, doc generation) with manual review before merging. Creates a self-improving flywheel.

Gitea Considerations

Most community examples use GitHub Actions with @claude mentions. For Gitea:

Gitea Actions (compatible with GitHub Actions syntax) could run headless Claude
Webhook-based triggers for PR review
Would need to evaluate Gitea MCP compatibility or build a simple API wrapper skill

1.6 KiB Raw Blame History