Sr Harness
- Updated July 27, 2026
- SeokRae/sr-harness
sr-harness is a custom coding-agent harness plugin that enforces stage-entry checkpoints across brainstorm-to-PR workflows so developers get predictable issue-driven delivery in Claude Code.
About
sr-harness is a Claude Code and Codex plugin that lets you design how your coding agent works instead of relying on passive background rules. It chains skills for brainstorm, plan, GitHub issue creation, Karpathy-gated execution, intent analysis, verification, and PR submission with optional pause handoffs between sessions. Use it when issue-driven development keeps breaking down because planning, implementation, and review feel like disconnected sessions without enforced checkpoints.
- Issue-driven flow: 1 Issue = 1 Branch = 1 PR with Closes #N
- Karpathy four-rule checkpoints enforced at stage entry
- Skills from start through finish including pause handoff and ralph loop
- Stack auto-detection loads dev-stack-java for Gradle or Maven projects
- Available for Claude Code and Codex via shared SKILL.md manifests
Sr Harness by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin marketplace add SeokRae/sr-harnessAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Last updated | July 27, 2026 |
|---|---|
| Repository | SeokRae/sr-harness ↗ |
How do I make my coding agent consistently follow issue-driven development with enforced checkpoints instead of drifting across disconnected brainstorm, code, and PR steps?
Enforce an issue-driven Claude Code workflow from brainstorm through plan, execute, verify, and PR with Karpathy checkpoints at each stage.
Who is it for?
Developers who want a structured GitHub issue-driven Claude Code workflow with explicit verify conditions and surgical-change enforcement.
Skip if: Teams avoiding GitHub Issues, branch-per-feature discipline, or multi-skill orchestration overhead.
What you get
Produces GitHub issues and branches, step-verified implementation commits, intent-analysis reports, integration verification, and PRs with Closes #N in the body.
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
FAQ
What workflow does Sr Harness enforce?
It routes sessions through brainstorm, plan, issue, execute, debug, analyze, verify, submit, review, and finish with Karpathy checkpoints at key stages.
How does issue-driven development work here?
Create one GitHub Issue and branch per change, commit with (#N) references, and close issues via Closes #N in the PR body—not commit messages alone.
Can I hand off mid-session?
Yes—the pause skill suspends work and prepares context for the next session to resume the same lifecycle.