Turn GitHub Issues
Into validated PRs
Maps your full codebase, scopes the change, builds in an isolated branch, runs validation, and delivers a review-ready Pull Request — all inside GitHub.
No chat prompts. No direct main writes. No automatic merge.
How Codingship Agent works
Issue in → CodeGraph scan → scope review → approval → build → PR out.
Open a GitHub Issue
Describe the change directly in GitHub. No extra tools or chat required.
CodeGraph full repo scan
Maps file structure, dependencies, and call chains to define exact change boundaries.
Scope & price review
Shows files in scope, risk level, validation plan, and PR complexity price.
You approve the task
Reply /approve to start. No approval, no code changes ever happen.
Builds in isolated branch
Works strictly inside approved scope, runs lint, build and test checks.
PR ready for your review
Opens a PR with full delivery report. You review, request changes, or merge.
You approve the scope before any code changes
Every task starts with a CodeGraph-backed scope review. You see exactly what will change, why, and what it costs.
Scope Review
- app/orders/page.tsx
- components/orders/export-button.tsx
- lib/orders/export-csv.ts
- tests/orders-export.test.ts
CodeGraph defines boundaries
Exact file scope is mapped before execution, no out-of-scope changes.
No approval, no work starts
Codingship never begins execution without your explicit /approve.
No direct writes to main
All work happens in an isolated task branch, never on your main branch.
No automatic merge
You always control what gets merged into your codebase.
No PR created, no PR charge
If Codingship cannot deliver a PR, you are not charged for that task.
Built for PR delivery, not code snippets
CodeGraph-powered scoping, strict boundaries, validation-first delivery, and clear per-PR billing.
GitHub Issue Intake
Turns GitHub Issues into structured engineering tasks before execution.
CodeGraph Repo Scan
Maps file dependencies and call chains to define exact change boundaries.
Scope & Risk Review
Shows expected files, risk level, validation plan, and price before work starts.
Pay per PR
Pricing based on PR complexity: Simple, Medium, or Complex.
Branch Isolation
All work runs in a separate task branch, never directly on main.
Validation before PR
Runs configured lint, build and test checks before opening a Pull Request.
PR Delivery Report
Every PR includes summary, changed files, validation results and review notes.
Failure Transparency
If delivery fails before PR creation, Codingship explains why and does not charge.
Every PR comes with a delivery report
Codingship does not just generate code. It delivers a reviewable PR package.
Reviewable, not black-box
Every Pull Request ships with a structured delivery report that explains what changed, why those files were selected, what validation ran, and what risks to watch for.
The goal is not to hide AI behind a black box. The goal is to make every change easier for your team to review, audit, and confidently merge.
- Summary of changes
- Files changed (CodeGraph verified)
- Why these files changed
- Validation results
- Risk notes
- Review checklist
- Rollback notes
Designed for teams that care about control
Codingship works inside GitHub's normal review workflow, with clear boundaries before execution.
No direct main writes
Codingship works in a separate task branch. All changes go through Pull Request review.
No automatic merge
The agent opens a PR. You decide what gets merged. No auto-merge, no surprises.
GitHub login only
Users sign in with GitHub. No passwords, no separate accounts, no extra credentials.
GitHub App access
Repository access is handled through the GitHub App installation with granular permissions.
Scope before execution
You approve the scope and PR complexity before any code changes begin.
No PR, no charge
If Codingship cannot create a PR, you are not charged for that task.
Simple pricing by Pull Request complexity
No token math. No confusing credits. You pay based on the PR Codingship delivers.
Includes
- Issue analysis
- Scope review
- Code change
- Basic validation
- Pull Request creation
Includes
- Everything in Simple
- CodeGraph repo scan
- Multi-file scope review
- Validation report
- PR delivery summary
Includes
- Everything in Medium
- Deeper CodeGraph analysis
- Risk review
- Extended validation loop
- Detailed delivery report
Frequently asked questions
Does Codingship understand my existing codebase before writing code?
Yes. Codingship analyzes repository structure, existing patterns, related files, dependencies, and validation commands before proposing a scope review.
How does Codingship decide which files to change?
It maps the issue to existing architecture patterns and explains why each expected file belongs to the task before execution.
Does Codingship write directly to main?
No. Codingship works in a separate branch and opens a Pull Request. You review and merge.
When do I pay?
You pay based on PR complexity after you approve the scope and Codingship creates a Pull Request.
What happens if no PR is created?
No PR created, no PR charge. Credits are released automatically.
Turn your next GitHub issue
into a Pull Request
Install the GitHub App, connect a repository, open an issue, and let Codingship prepare a scoped PR for review.
No PR created, no charge.