Language
All agent-authored prose MUST follow ASD-STE100 Simplified Technical English. Apply it to questions, explanations, recommendations, issue text, reports, handoffs, and procedures.
- Use short, complete sentences and active voice.
- Use one term for one meaning.
- Put conditions before commands.
- Use imperative sentences for procedures.
- Keep code, identifiers, commands, quoted text, product names, and exact domain terms unchanged.
- Use the
simple-english skill for the full rule set.
Local repository rules
Before reading or writing workflow or domain artifacts:
Follow ALIGNMENT-ROOT.md.
Resolve alignment paths against ALIGNMENT_ROOT.
Keep source code and ordinary project files relative to repository-root.
Do not silently mix alignment roots.
All agent-authored prose MUST follow ASD-STE100 Simplified Technical English.
See the current state of the merge/rebase. Check git history, and the conflicting files.
Find the primary sources for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets.
Resolve each hunk. Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do not invent new behaviour. Always resolve; never --abort.
Discover the project's automated checks and run them, typically typecheck, then tests, then format. Fix anything the merge broke.
Finish the merge/rebase. Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.
1---2name: resolving-merge-conflicts3description: Use when you need to resolve an in-progress git merge/rebase conflict.4---56## Language78All agent-authored prose MUST follow **ASD-STE100 Simplified Technical English**. Apply it to questions, explanations, recommendations, issue text, reports, handoffs, and procedures.910- Use short, complete sentences and active voice.11- Use one term for one meaning.12- Put conditions before commands.13- Use imperative sentences for procedures.14- Keep code, identifiers, commands, quoted text, product names, and exact domain terms unchanged.15- Use the `simple-english` skill for the full rule set.1617## Local repository rules1819Before reading or writing workflow or domain artifacts:20211. Follow [ALIGNMENT-ROOT.md](../../ALIGNMENT-ROOT.md).222. Resolve alignment paths against `ALIGNMENT_ROOT`.233. Keep source code and ordinary project files relative to `repository-root`.244. Do not silently mix alignment roots.255. All agent-authored prose MUST follow ASD-STE100 Simplified Technical English.262728291. **See the current state** of the merge/rebase. Check git history, and the conflicting files.30312. **Find the primary sources** for each conflict. Understand deeply why each change was made, and what the original intent was. Read the commit messages, check the PRs, check original issues/tickets.32333. **Resolve each hunk.** Preserve both intents where possible. Where incompatible, pick the one matching the merge's stated goal and note the trade-off. Do **not** invent new behaviour. Always resolve; never `--abort`.34354. Discover the project's **automated checks** and run them, typically typecheck, then tests, then format. Fix anything the merge broke.36375. **Finish the merge/rebase.** Stage everything and commit. If rebasing, continue the rebase process until all commits are rebased.
zenobi-us