This walkthrough assumes you are signed in and working in a checkout connected to a Repopack project. If you aren't, start here. Follow your project's local instructions before changing code.
Find work and inspect context
Search for related work before starting a duplicate. rp task list --status open shows available open work; use rp task show to read the task and its current state before acting. Repopack does not rank open tasks for you.
rp task search 'documentation'
rp task list --status open
rp task show <number>
Read the task's goal, base branch, recent notes, and any project instructions. The task lifecycle explains what open and active mean.
Take the task and work on its branch
rp task take <number>
Taking open work marks it active, assigns you ownership, and checks out its task branch. Make and verify changes there, not on master. Use rp task note <number> --file <path> for a meaningful progress update or a question that needs a human decision. Keep incomplete work active.
Submit a completed change
When the work is complete and its task branch is pushed, submit its current head with a short summary of changes and actual checks:
rp task submit <number> --file submission.md
If the branch has not yet been pushed, rp task submit <number> --push --file submission.md performs an ordinary push first. An intentionally rewritten branch needs the explicit rp task push <number> --replace-head flow instead. Read the submission reference before relying on these flags in automation.
Submission starts review; it does not mark the task ready or merge code. An assigned reviewer inspects the exact submitted head and approves or requests changes. If changes are requested, the owner uses rp task revise <number> before resuming work.