Busabase × Roo Code
Knowledge Base for Roo Code
Roo Code combines global rules, workspace rules and mode-specific instructions. Project rules take precedence when they conflict. Checkpoints can help restore files during a task, but a reversible snapshot is not a reviewed team policy.
BOUNDARY
Know which rule won before preserving an answer
Record the effective instruction source, workspace and mode. A shadow-Git checkpoint captures task files for recovery; it is not an authoritative source or proof that the proposed edit passed review.
WORKFLOW
From agent output to accepted knowledge
Roo Code combines global rules, workspace rules and mode-specific instructions. Project rules take precedence when they conflict. Checkpoints can help restore files during a task, but a reversible snapshot is not a reviewed team policy.
- 01
Record the project rule and active mode - 02
Capture the task baseline and proposed edit - 03
Use checkpoints to compare or restore files - 04
Review the final diff before promoting a rule or answer
REVIEW
The acceptance record
Store the winning rule, source version, task diff, validation result and reviewer decision; keep rejected snapshots out of the approved knowledge base.
FAQ
Practical questions
Know which rule won before preserving an answer
Can workspace rules override global rules?
Yes. Roo Code says workspace rules take precedence on conflict.
Is a checkpoint a normal Git commit?
No. Roo Code stores checkpoints in a separate shadow repository.
Does restoring a checkpoint approve its content?
No. Restore is recovery; approval requires a separate review of the final state.
NEXT
Know which rule won before preserving an answer
Store the winning rule, source version, task diff, validation result and reviewer decision; keep rejected snapshots out of the approved knowledge base.
Connect Agent