Bounties & workflow
Submitting a pull request
A submission isn't just code — it's a structured PR the review pipeline can reason about.
FORKE_SUBMISSION.md
Forke auto-generates this template in your branch. Fill it in before opening the PR — it has five sections:
What I Changed— required, minimum two bullet pointsWhy I Made These Choices— required, explain key decisionsTesting Performed— requiredKnown Limitations— optional but encouragedScreenshots / Demo— optional, strongly encouraged for UI tasks
This file does three jobs: it forces you to think about what you built, it gives the AI reviewer structured context, and it becomes part of your portfolio entry. A missing or empty required section fails the automated layer before any AI is called.
After you submit
The moment the PR opens, the pipeline runs in order:
- Automated validation (build, tests, lint, type-check, security scan, scope check)
- Context assembly (task, acceptance criteria, diff, repo patterns, your history)
- AI review → a structured verdict
- Risk scoring → routes to auto-approve, owner review, or trusted reviewer
Track everything from My Submissions, grouped by Active, Completed, and Revision Requested.
NoteFull detail in the review pipeline.
