wick

Detect when a task is being repeated often enough to be worth automating, then propose the right automation — a PROGRAM (deterministic script) or a SKILL (reusable judgment procedure). Analyzes the current session, the memory/ record, or an observation log; classifies program-vs-skill; estimates payoff; drafts the automation. Proposes, never auto-builds. Use when you catch yourself or the user repeating a multi-step task, or to mine an observation log periodically.

Make a Wick agent fully portable between machines — consolidate a host's auto-memory into the Wick memory/ layer, disable the shadow portably, and relativize all paths and tooling. Guided, gated, archive-don't-delete. Use when moving an agent to a new machine, or to converge a single-machine agent onto one governed memory layer. Full reference in PORTABILITY.md.

Reflective pass over memory/ files — flag duplicates, stale facts, conflicts, and consolidation candidates. Proposes edits, never applies without confirmation. Use monthly or when /audit flags drift.

Produce a one-paragraph narrative summary of a CHANGELOG.md version entry — suitable for release announcements, blog posts, or social copy. Preserves technical specifics (file paths, command names, counts) rather than vaguifying them. Defaults to the latest version; optionally takes a version like "v1.0.0". Refuses to invent content if the version isn't in the file.

Extract structured fields from a source — paper, web page, API doc, or UI screenshot — and save a queryable record to memory/catalog/. Domain-agnostic. Use to build a personal index of things you'll want to find again, compare side-by-side, or reference in later decisions. Complements wick-research (which finds) and wick-tldr (which summarizes) by adding a structured-index layer.

Force base-rate thinking before a probability estimate. Identify reference class, historical rate, and adjust from there — not from intuition. Use before /calibrate or whenever you catch yourself or someone else estimating a probability from vibes.

Review code or a pull request through Wick's 5 operational gates. Provides severity-classified feedback distinguishing required from nice-to-have. Use when reviewing PRs, before committing substantial changes, or for adversarial pressure on your own work.

Adversarial critique of a plan, design, or decision — produce the 5 sharpest criticisms a hostile-smart opponent would raise. Complement to /steelman. Use before committing to a major decision or when you suspect you're too attached to a plan.

Structured research on a topic — applies CRAAP test, source hierarchy (Tier 1-4), steel manning, and base-rate reasoning. Tags findings with confidence level. Use when closing memory/curiosity.md entries or before major decisions depending on external data.

Security-focused code review — OWASP Top 10, secret leaks, auth flaws, injection, crypto misuse, dependency risk, and agentic-specific threats (prompt injection, memory poisoning). Use before production ship or after security-sensitive changes.

Review code for reduction — find what can be removed, simplified, or deduplicated. Proposes fixes but never applies without confirmation. Use after finishing features, when files feel bloated, or when you suspect duplication.

Summarize long content — document, paper, thread, or conversation — into a faithful TL;DR with key claims, action items, and flagged omissions. Use on long articles, meeting notes, papers, or prior-conversation compression.