Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
npx claudepluginhub seokrae/sr-harness --plugin sr-harness작업 중단 및 브랜치 정리 스킬. "그만할게", "방향 바꿀게", "이 작업 취소", "브랜치 정리" 시 사용. session-plan Deviations 기록 + 브랜치 삭제 여부 확인. 어느 단계에서든 진입 가능.
아이디어를 작고 명확하게 구체화하는 반복 피드백 루프 스킬. 아이디어 탐색, 기능 설계, 방향 논의 시 사용. "뭔가 만들고 싶어", "어떻게 접근할까", "좋은 방법이 없을까" 같은 표현에서 즉시 실행.
버그, 테스트 실패, 예상 밖 에러 발생 시 진단 우선 디버깅 스킬. "에러가 났어", "테스트 실패", "왜 안되지", "버그" 시 즉시 실행. karpathy §1 진단 우선 + 실패 분석 원칙 내장.
아키텍처 설계 원칙 체크리스트. execute 시작 전 또는 설계 중 참조. Hexagonal Architecture·레이어 분리·패키지 구조 세 섹션으로 구성. Keywords: 아키텍처, hexagonal, 레이어, 패키지, 설계, architecture, layer, package, ports and adapters
코딩 품질 원칙 체크리스트. execute 시작 전 또는 코드 작성 중 참조. 네이밍·예외 처리·테스트 세 섹션으로 구성. Keywords: 코딩 원칙, 네이밍, 예외처리, 테스트, 품질, coding standards, naming, exception, test
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Harness-native ECC plugin for engineering teams - 64 agents, 262 skills, 84 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Claude Code skills for Godot 4.x game development - GDScript patterns, interactive MCP workflows, scene design, and shaders
Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
7-Phase Context Engineering plugin: a single pipeline to collect, select, structure, compress, generate, and verify AI context.
착수보고서(Project Charter) 체크리스트 기반 검토 플러그인. PM 표준 기반으로 완성도·모호성·일관성·리스크를 분석한다.
JD(채용공고) 기반 이력서 맞춤 최적화 스킬. JD를 채점 기준표로 분석하고 경험을 PHER 구조로 재구성한다.
Generate self-contained HTML visualizations from documents and data
Obsidian 제텔카스텐 + 프로젝트 문서 관리 플러그인 — capture·study·wiki·lint-wiki·daily·weekly·retro·scaffold·iss·hub·wbs·history·visualize·audit·migrate·search·archive·defuddle·canvas·obsidian-bases
A custom coding-agent harness for designing how your AI assistant works — not the other way around.
English | 한국어 | Interactive Workflow →
When working with coding agents day-to-day, the same patterns keep breaking down:
sr-harness structures these into a single workflow where each stage enforces the right behavior automatically.
Instead of relying on rules loaded somewhere in context, each skill applies checkpoints at stage entry.
execute: before touching code
[ ] Is the request clear? If not → ask first
[ ] Is there a simpler path? If yes → propose it
[ ] Is there a success criterion? If not → define it
execute: when editing existing code
[ ] Read the file before writing
[ ] Only touch lines directly related to the request
[ ] Leave surrounding code, comments, and formatting as-is
From idea to PR, each skill hands off naturally to the next.
sr-harness ships manifests for both Claude Code and Codex:
.claude-plugin/plugin.json.codex-plugin/plugin.json# Add marketplace
claude plugins marketplace add https://github.com/SeokRae/sr-harness.git
# Install
claude plugins install sr-harness@sr-harness
Verify:
claude plugins list
# ❯ sr-harness@sr-harness
# Version: 0.17.3
# Scope: user
# Status: ✔ enabled
Codex support is manifest-ready through .codex-plugin/plugin.json. Install it through your Codex plugin marketplace or local plugin source configuration. Once installed, the shared skills/*/SKILL.md files are available to Codex.
Runtime-specific behavior is documented in docs/RUNTIME-COMPATIBILITY.md.
The full lifecycle — state transitions, the skill map, resolved gaps, and the remaining roadmap — is documented in docs/LIFECYCLE.md.
start
│ Identify task type, load session plan, route to the right skill
│
├─ brainstorm
│ Not: dump all ideas at once
│ But: one round = one concrete output + one clarifying question
│ Exit: idea is small enough to fit in a single GitHub Issue
│
├─ plan
│ Every step must have a verify condition
│ Format: "do X → verify: [done criteria]"
│ No verify = step doesn't go in the plan
│
├─ issue
│ Create GitHub Issue → branch from origin/main
│ Rule: 1 Issue = 1 Branch = 1 PR
│ No chain branches. No multi-issue branches.
│
├─ execute ←─────────────────────────┐
│ Karpathy checkpoints at stage entry │
│ step → verify → commit → next step │
│ │
├─ debug ────────────────────────── ┘
│ Diagnose before touching code
│ Never retry the same failing approach twice
│
├─ verify
│ Integration check before submitting
│ git status · changed files · test suite
│
├─ submit
│ push → PR with "Closes #N" in body
│ Stops here. User reviews the PR.
│
├─ review
│ Receive review feedback → back to execute
│
└─ finish
Merge + delete branch + pull main
The work is truly done.