Commit after review#

A Helmor workspace should end with a reviewed result. Commit only after the session output, file diff, and verification all line up.

Before committing#

• Confirm the task goal is complete.
• Inspect changed files for unrelated edits.
• Run the focused tests, typecheck, or build command that fits the change.
• Write a commit message that describes the actual result.

Shipping with GitHub#

When the workspace is connected to GitHub, use the target branch and repository context to prepare work for review. Keep the pull request focused on the same task the workspace was created for.

If the diff grew too large#

Do not force it through. Split the work, continue the session with narrowing instructions, or create a new workspace for follow-up changes.