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 points
• Why I Made These Choices — required, explain key decisions
• Testing Performed — required
• Known Limitations — optional but encouraged
• Screenshots / 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:

1. Automated validation (build, tests, lint, type-check, security scan, scope check)
2. Context assembly (task, acceptance criteria, diff, repo patterns, your history)
3. AI review → a structured verdict
4. Risk scoring → routes to auto-approve, owner review, or trusted reviewer

Track everything from My Submissions, grouped by Active, Completed, and Revision Requested.