Yeachan-Heo
Grades are signals, not a certification. Always review a skill yourself before use.
Is this you?
These skills are attributed to Yeachan-Heo on SkillRepo. If that’s your GitHub account, sign in with GitHub to move them into your account — they’re already here, and it never touches your GitHub repos.
Sign up free to publish unlimited skills, graded and attributed to you.
Get StartedSearching by meaning· free account to run
97 skills found
Settle types and module shape before cross-boundary code — competing designs explored in parallel, compared on API surface and invariants, decision recorded wit… more
Periodic architecture survey — walks the module graph and reports ranked deepening candidates (shallow modules, hypothetical seams, logic behind the wrong seam)… more
Run N parallel candidates at one brief and synthesize: rubric-first framing, isolated fan-out, a cross-judge on a different model, criterion-by-criterion pick,… more
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then… more
Drive an open PR to merge-ready on the watch-pr verdict policy — watch checks and review state, fix CI, address comments; never merges, rebases, or force-pushes… more
Vet a measured number before reporting or acting on it: name the limiter, measure the claimed work, repeat with variance, rule out the observer, label every cla… more
Map what a change could break beyond the diff — dependents found by search and AST, classified certain/likely/unlikely — and prove the certain and likely ones b… more
Restate the last technical message in plain human language — no jargon, no shorthand, every fact and number kept. For 'say it plainly' or when a reply was too d… more
Find the mistakes agents keep repeating in this repo and make each impossible at the highest enforcing level — lint rule, type guard, runtime check, script, the… more
Verify the project's riskiest invariant with TLA+, Lean, or Kani — chosen by property shape — and leave a project-local skill the next agent reruns; assumptions… more
Generate the project's own verify skill: build/test/lint commands discovered by running them, a feature map of what each covers, manual checks, and an earned fi… more
Use the smallest visual when prose must carry structure—control flow, call depth, module ownership, or change shape: pseudocode, call tree, component/file tree,… more
Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards), seeded as two faces on day one (CLAUDE.md… more
Design a rigorous bespoke playbook for a task no bundled skill fits — steps that each end in a check, verification commands, failure branches — stored where the… more
Find the failing checks on the current PR, read their logs, classify the failure (real / flaky / environmental), fix the real ones with focused changes, and rer… more
Resolve merge conflicts non-interactively: start the integration, read both sides' intent from their commits, preserve both intents, validate on the resolved tr… more
Fetch and triage review threads on a PR: threads deduped with resolution state, each with a fix/dismiss/ask recommendation, bot findings read skeptically. Befor… more
Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses… more