HECer

HECer/yoke

Plugin Claude Code

Plugin marketplace listing 1 plugin: yoke.

HECer/yoke

Plugin Claude Code

Cross-agent coding harness: one curated skill canon (TDD, brainstorming, plans, reviews, shipping, design verification) plus mechanical safety gates and an autonomous loop via the yoke CLI.

HECer/yoke

Skill Claude CodeCodex

Use when turning a product idea or change into a loop-ready continuous backlog with small stories and executable behavioral evidence.

HECer/yoke

Skill Claude CodeCodex

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

HECer/yoke

Skill Claude CodeCodex

Design or improve deep modules, small interfaces, real seams, and public-interface tests. Use when shaping a module, placing a dependency seam, evaluating shallow pass-through layers, improving testability, or comparing architecture alternatives; do not force unrelated refactors.

HECer/yoke

Skill Claude CodeCodex

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.

HECer/yoke

Skill Claude CodeCodex

Post-ship documentation update. Runs after ship (code committed, PR exists) but before the PR merges. Updates every documentation file to reflect the changes in the diff: README, CHANGELOG, ARCHITECTURE, CONTRIBUTING, TODOS.md, VERSION. Use when asked to "update docs", "document the release", or "update the changelog".

HECer/yoke

Skill Claude CodeCodex

Build or sharpen a project's domain language and durable decisions. Use when terminology is fuzzy or contradictory, relationships need scenario testing, the code disagrees with the stated model, or a glossary or ADR-class decision must be updated; do not trigger merely to read existing context.

HECer/yoke

Skill Claude CodeCodex

Use when you have a written implementation plan to execute in a separate session with review checkpoints.

HECer/yoke

Skill Claude CodeCodex

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.

HECer/yoke

Skill Claude CodeCodex

Code Quality Dashboard. Runs the project's type-checker, linter, test runner, and dead-code detector, scores each category 0-10, and presents a dashboard with trends. Use when asked for a "health check", "code quality report", or "quality dashboard".

HECer/yoke

Skill Claude CodeCodex

Use at the start of any substantial task and whenever you make a non-obvious decision or learn a reusable fact — keeps .yoke/context/ (PROJECT, DECISIONS, KNOWLEDGE) the durable source of truth so fresh-context work never drifts.

HECer/yoke

Skill Claude CodeCodex

Use before writing any code — write the least code that fully solves the task (YAGNI, stdlib-first, no unrequested abstractions) to save tokens and reduce maintenance.

HECer/yoke

Skill Claude CodeCodex

Edit prose into clearer, more direct writing while preserving the writer's voice, or detect named AI-slop patterns without rewriting or guessing authorship. Use for documentation, release notes, product copy, or prose audits; do not trigger for code-only work.

HECer/yoke

Skill Claude CodeCodex

Use when a task has efficiency requirements or touches a hot path — make performance a measured requirement (benchmarks as tests, budgets as gates), keep interfaces clean and optimizations local, and version the WHY so future agents don't "clean up" fast code back to slow.

HECer/yoke

Skill Claude CodeCodex

Mega plan review from a product/CEO perspective. Challenges premise, challenges scope, maps alternatives, reviews architecture through 11 sections, and offers an outside voice. Use when asked to "CEO review", "mega plan review", "product review this plan", or when shipping a significant new product feature.

HECer/yoke

Skill Claude CodeCodex

Engineering plan review. Reviews a plan document for architecture, code quality, test coverage, and performance before implementation begins. Produces a coverage diagram, failure modes map, and parallelization strategy. Use when asked to "review this plan", "eng review", or "architecture review".

HECer/yoke

Skill Claude CodeCodex

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.

HECer/yoke

Skill Claude CodeCodex

Use when completing tasks, implementing major features, or before merging to verify work meets requirements.

HECer/yoke

Skill Claude CodeCodex

Resolve an in-progress Git merge or rebase conflict by tracing both sides to commits and available issue or spec evidence, preserving compatible intent, and running project checks. Use only when a merge or rebase is currently conflicted.

HECer/yoke

Skill Claude CodeCodex

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics for the time window. Team-aware: identifies the user, then analyzes every contributor with per-person praise and growth opportunities. Use when asked for a "retro", "engineering retrospective", or "weekly summary".

HECer/yoke

Skill Claude CodeCodex

Pre-merge code review — the single canonical review of a change before it lands. Covers BOTH diff safety/structure (SQL safety, LLM trust-boundary violations, conditional side effects) AND engineering quality (architecture fit, edge cases, test coverage, performance). Use when asked to "review this PR", "code review"…

HECer/yoke

Skill Claude CodeCodex

Fully automated ship workflow. Merges the base branch, runs tests, audits coverage, reviews the diff, generates a CHANGELOG entry, bumps the version, commits, pushes, and creates the PR. Use when asked to "ship", "create a PR", or "open a pull request".

HECer/yoke

Skill Claude CodeCodex

Use when executing implementation plans with independent tasks in the current session.