End of turn marker
Linlin's curated AI agent harness configuration: workflow rules, skills, hooks, plugin recommendations, tooling preferences, and project templates. Loadable into any new project so a fresh /init can pick the relevant subset.
npx -y skills add jajupmochi/agent-harness --skill end-of-turn-markerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Every turn MUST end with a visible divider header followed by numbered summary items. Use [END:FINAL], [END:WAIT], or [END:NEEDS_USER] embedded in the divider.
SKILL.md
1.5 KB, as published. Nobody here has run it
end-of-turn-marker
Every user-facing turn ends with a divider block. The divider is the SECTION HEADER. Numbered summary items follow below it.
Format
━━━━━━━━━━━━━━━━━━━━
✅ 完成 · Complete
━━━━━━━━━━━━━━━━━━━━
1. First change or fix
2. Second change or fix
3. Third change or fix
OR:
━━━━━━━━━━━━━━━━━━━━
🤚 需要用户 · Needs User
━━━━━━━━━━━━━━━━━━━━
1. 需要确认：merge 到 main？
2. 有 3 个文件未提交，是否推送？
OR:
━━━━━━━━━━━━━━━━━━━━
⏳ 等待中 · Waiting
━━━━━━━━━━━━━━━━━━━━
1. dev server 运行在 port 3000
2. 等待测试完成后继续
Rules
- The divider block is ALWAYS at the very end of the turn
- Numbered items follow the divider, one per line
- Use [END:FINAL], [END:WAIT], or [END:NEEDS_USER] as the LAST line after all items
- Never put content AFTER the [END:*] marker
- If review-gate fires, its output replaces/supplements the summary items
Integration with review-gate
The review-gate Stop hook output should format neatly with the marker divider.