Verbalized Sampling (VS) protocol for deep intent exploration before planning. Use when starting ambiguous or complex tasks, when multiple interpretations exist, or when you need to explore diverse intent hypotheses and ask maximum clarifying questions before committing to an approach.

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.

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

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.

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.

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

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".

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.

Produce share-safe copies of memory files under /tmp, with PII redacted (absolute paths, emails, session IDs, old dates) and credentials scanned (API tokens, keys). Never mutates originals. Use this skill when the user says "sanitize memory for sharing", "redact memory PII", "scan memory for credentials", "share my memory", "export safe memory", or "make memory shareable".

Scan the active agent's session-history transcripts to surface save-worthy signals (corrections, revealed preferences, project decisions, external references), then propose and write auto-memory files with valid frontmatter and a synchronized MEMORY.md index entry. Use this skill when the user says "save this to memory", "add a memory", "remember that", "update memory file", "scan this session for memories", "what should we remember from this session", or "promote this correction to memory".

Decompose a task into independent concerns and execute them through broadly parallel, specialized agent groups. Use when a request involves multiple independent sub-tasks, research across separate domains, or work that can be parallelized across files or modules.

Software architect and planning specialist - conduct thorough read-only planning before any action. Use when exploring a codebase to design implementation plans, defining objectives, gathering relevant files, and summarizing available tools before coding begins.

Merge one or more PRs into the base branch with queue-like sequencing and conflict resolution. Use when merging PRs that may conflict with each other or the base, requiring ordered application and intelligent conflict handling.

Merge multiple PRs into a temporal integration branch before merging to base, with ordered conflict resolution. Use when you want to validate a set of PRs together on a staging branch before advancing the base branch.

Review code changes on a given GitHub PR using gh CLI. Use when the user asks to review a pull request, analyze PR diffs, or provide feedback on open PRs with structured quality, security, and testing assessments.

Tests are not assets. Tests are liabilities that pay rent by catching real bugs. Volume is not a quality signal — coverage percentage is not a quality signal — only the counterfactual matters: **if I delete this test, can a real bug now reach prod?** If the answer is no, the test is dead weight,