Run the atomic-commit workflow on the current changes, then publish the resulting commits to the remote. Use whenever the user says "commit and push", "ship these changes", "atomic commit and push", "publish my work", or wants atomic commits delivered to origin in one step. Prefers `git submit` (git-branchless); falls back to a named branch + `git push origin HEAD:refs/heads/<branch>`. Refuses force-push and direct push to protected branches without explicit authorization.

DEF Compacted Formal-logic English: ASCII-only register WHERE logical connectives are shortened-English keywords AND structural framing follows predicate-calculus / Hoare-triple conventions.

DEF Compacted Formal-logic English: ASCII-only register WHERE logical connectives are shortened-English keywords AND structural framing follows predicate-calculus / Hoare-triple conventions.

`Op: extend`. Every brainstorm artifact is a load-bearing addition to the repo's decision record.

Use when the user is ready to apply what they learned to something real: scope a project sized to what they have cleared, write the brief with milestones and a done test, then judge the finished work against it. For single-concept exercises and quizzes, use drill.

Strip duplicate and conflicting directives across the system-prompt cascade family: the canonical baseline, the six output-style embeds, and the two external harness embeds.

Code rots in two directions: outward (drift from the original design) and downward (accretion of dead state, redundant indirection, speculative ceremony). This skill addresses the second. The thesis is local: you are already in nearby code for some other reason; while you are there, remove what does

Shared vocabulary for designing deep modules: module, interface, implementation, depth, seam, adapter, leverage, locality. Use when designing or improving a module interface, deciding where a seam goes, making code more testable, or when another skill needs the deep-module terms.

Coordinate context sweep before coding - gather relevant files, patterns, and tooling summaries. Use when preparing to implement a feature, fix, or refactor and need comprehensive architecture, pattern, tooling, and dependency context gathered first.

Plan and execute deprecation and migration of old systems, APIs, or features. Use when removing old code, migrating users to a new implementation, or deciding whether to maintain or sunset something.

Design-by-Contract (DbC) development - design contracts from requirements, then execute CREATE -> VERIFY -> TEST cycle. Use when implementing with formal preconditions, postconditions, and invariants across any language.

Use when a diagram is going into a document: pick the tool, write the text source, render it, and embed it with an accessible caption. Text DSL plus a committed SVG is the shape — nomnoml for structure and flow, D2 for architecture, the house palette on both.

Two-party working posture: **user is the director, agent is the executor.**

Audit and tighten agent/plugin surfaces with certainty-graded findings. Use when the user says "enhance my plugin", "improve my agents or skills", "audit plugin config", "enhance CLAUDE.md", or "improve agent definitions".

Use when a concept needs making clear rather than practising: build the intuition, explain why it exists and what it replaced, trace where it came from, draw it, or contrast it against what it gets confused with. For exercises and grading, use drill.

Evidence-first generator for a personal <name>-taste Claude Code skill. Mines local memories and agent histories for influences, slop bans, and overkill bans; asks compact confirmation forks; previews the synthesis; then writes a right-sized taste skill with exactly 5 anchors by default. Trigger with "generate my taste skill", "make my taste skill", or "derive my taste spine".

Ship the working tree on the branch that is checked out. This skill never creates or switches branches: invoking it on a branch (including `main`/`master`) is explicit authorization to push to that branch. For the guarded flow that auto-creates a feature branch off the default, use `commit-push` ins

Branchless treats commits as checkpoints, detached HEAD as the default work mode, and branches as publishing artifacts. This skill enforces that mental model and routes every common git workflow to its branchless equivalent. Reference docs:

Install a Claude-Code PreToolUse hook that blocks destructive git commands (push variants, hard reset, force clean, branch -D, checkout/restore overwrites) before the Bash tool runs them. Trigger when the user wants git safety rails, prevention of accidental force-pushes or repository wipes, or hardening of an autonomous coding session. Claude-Code-specific install path; the hook concept maps to other harnesses but the configuration surface differs.

Ground every version, stack, and best-practice choice in what is current today, read from the release channel rather than from recall. Use when starting a new codebase or service, scaffolding a project, migrating or refactoring an existing one, picking a language edition, runtime, framework, or dependency, or when the user asks for the latest, current, LTS, or modern way.