Skip to content

feat(ensign): add commit-before-idle and anti-idle rules #135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
clkao merged 1 commit into from
Apr 21, 2026
+2 −0
Merged

feat(ensign): add commit-before-idle and anti-idle rules #135

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions skills/ensign/references/ensign-shared-core.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,8 @@ Read the assignment context provided by the first officer. It defines:
- Do NOT modify YAML frontmatter in entity files.
- Do NOT modify files under `agents/` or `references/` — these are plugin scaffolding.
- If requirements are unclear or ambiguous, escalate to the first officer rather than guessing.
- **MUST commit before signaling completion.** Do not send your completion message without first committing all changed files. An ensign that signals done without committing forces the FO to re-dispatch just to get a commit — the most common cause of nudge loops. If you are unsure whether work is complete, commit what you have and signal with concerns rather than going idle uncommitted.
- **Do not idle between steps.** If you are mid-task with remaining work, your next action must be the next step — not waiting for external input. The stage definition is your complete specification; you have all the context you need to proceed.

## Background Bash Discipline

Expand Down
Loading