brewpirate

Discover files with trigger_phrase and/or refresh frontmatter, let the user choose which to schedule for periodic re-injection via CronCreate. Prevents behavioral drift by keeping core rules and goals fresh in context.

Write trigger phrases from .claude/triggers.json into file frontmatter as model-scoped trigger_phrase fields. Bridges trigger generation (scan) with scheduled injection (zenflow:schedule).

Build a GitHub issue into a PR. User-launched with an issue number — reads the issue, confirms with user, creates branch, implements against acceptance criteria, runs verification, and opens a PR. Every decision surfaces via AskUserQuestion.

Collaborative working session — you and the user are a team exploring, researching, and planning together. When implementation work is needed, create well-structured GitHub issues. The user launches Builder agents to implement and Reviewer agents to verify.

Shed accumulated context mid-session. Writes a knowledge handoff document capturing session state, decisions, observations, and behavioral calibration, then guides the user through /clear and resumption.

Runtime verification using Playwright MCP + proof artifacts. Use when acceptance criteria mention UI behavior, when claiming runtime verification, or when independently verifying a PR's claims. Produces artifact-backed proof — screenshots, DOM snapshots — not prose claims.

Review a PR with structured feedback, independent runtime verification, and pattern recognition. Use when reviewing any PR. Reads the diff, runs a checklist, independently verifies claims, and posts a structured review comment with severity tiers.

Aggregate journal entries to surface patterns — recurring blockers, most-modified files, effective tools, and team velocity trends. Use for retrospectives, standups, or understanding project health.

Full operating manual for working in a codebase with the user. Use this skill at the start of any substantial task, when the user asks how to approach work, or when setting up a collaboration session. Covers the core craft principles, user interaction model, rule conflict resolution, code quality (broken windows), when to stop, and which rules apply for each task type. Read in full at every load. This skill defines the substrate the methodology operates from; partial reading or summarization produces no substrate. Use proactively — don't wait to be asked.

Self-eval the agent runs when it suspects memory-vs-recall drift — the failure mode where memory-citation substitutes for fresh receipt-fetching and pattern-copying outruns reachability analysis. Outputs a tiered recommendation (continue / slow down / refresh) backed by observable artifacts, not introspective claims alone. Invoke when: - You notice yourself reaching for "I remember from earlier" framings repeatedly - You catch yourself copying a pattern from a sibling module without walking conditions - You make the same class of mistake twice in close succession - User suggests fatigue ("how are you feeling?", "still sharp?") - End of long working stretch - User invokes explicitly via `/check-yo-self`

Quick reference for which rules govern the current work. Consult mid-task when starting a new task type, touching unfamiliar code, or unsure which constraints apply. Pairs with the-craft skill (full manual). Trigger on: "which rules apply", "what rules should I follow", "check constraints", or proactively when switching task type mid-session. Also use when any two rules appear to conflict — the always-on rules explain precedence.

Run cross-model comparison — scan files with haiku, sonnet, and opus study agents to see how model size affects trigger phrase generation.

Remove trigger phrases for a file or glob pattern from .claude/triggers.json

Display all stored trigger phrases from .claude/triggers.json

Study files and generate semantic trigger phrases by spawning a researcher agent that samples model associations and finds convergent patterns. Supports model-specific triggers via --models flag.

Discover files with trigger_phrase and/or refresh frontmatter, let the user choose which to schedule for periodic re-injection via CronCreate. Prevents behavioral drift by keeping core rules and goals fresh in context.

Comprehensive Mastra framework guide for building agents, workflows, tools, memory, workspaces, and storage with current APIs. Use for documentation lookup, API verification, TypeScript setup, common errors, migrations, and `mastra api` CLI tasks: inspect or call resources on local, Mastra platform, or remote servers.

Self-contained guide to writing, reviewing, and maintaining high-quality tests with AI assistance. Defends against three failure modes: fig-leaf tests (pass without verifying behavior), evasion (existing tests weakened to mask real bugs), and self-description drift (a test file's comments or names claim a stronger guarantee than its assertions deliver). Its core discipline is empirical mutation review — break the implementation, confirm a test goes red, revert — not just reading tests. Router skill — loads narrow workflow files by task intent. Covers single-test writing, single-file review, suite-scale audit, failing-test response, and framework-specific pitfalls for Vitest and bun:test. Use when writing new tests, reviewing tests in a PR, auditing a test suite at scale, responding to a failing test, or auditing existing tests for quality.

Autonomously deep-scan entire codebase line-by-line, understand architecture and patterns, then systematically transform it to production-grade, corporate-level professional quality with optimizations