make-no-mistakes

Append completed work items to today's standup file. Accepts a description, PR number, Linear issue ID, or --reset flag as $ARGUMENTS.

Compose and post today's standup message to Slack, combining data from the standup file with interactive user input. Accepts "draft" as $ARGUMENTS to send as draft instead of posting directly.

Generate or update a TestSprite-compatible test-suite.json from use case documentation. Accepts a URL or file path as $ARGUMENTS.

Launch a Qt-based visual previewer for test-suite.json files. Auto-detects the suite in the current project, ensures PySide6 is installed, and opens an interactive table with filtering, detail pane, and CSV export. Accepts an optional path as $ARGUMENTS.

Execute E2E tests from a test-suite.json file. Selects the optimal runner for each scenario, produces immutable result files, and optionally reports to Linear or Markdown. Accepts a path to test-suite.json or a jq filter as $ARGUMENTS.

Bootstrap your day by scanning for pending next-day handoff files and guiding you through resuming where you left off.

Save full session context to a next-day handoff file so tomorrow's session can pick up exactly where you left off. Accepts a short label for the file as $ARGUMENTS.

Execute Linear issues with full discipline -- sequential branches, worktree isolation, reviewer loops, CI verification, and clean merges. Accepts one or more Linear issue IDs or URLs as $ARGUMENTS.

Bootstrap a Linear workspace with label taxonomy, projects, milestones, and reviewer integrations. Modes: labels, projects, audit, sync, or clean slate (default). Accepts mode as $ARGUMENTS.

Gather and present a prioritized, actionable list of everything pending from the current session, git state, Linear issues, and memory.

Run automated penetration tests following Cyber Kill Chain + OWASP methodology. Accepts a phase, OWASP category, or component as $ARGUMENTS.

Synchronize your entire local state (branches, worktrees, PRs) with the latest release after a team-wide rebase. Accepts a repo name as $ARGUMENTS.

Recall past decisions, feedback, and instructions from memory, CLAUDE.md, and project context. Accepts a topic or keyword as $ARGUMENTS.

Generate a structured recap of everything accomplished in the current session, including tasks completed, files changed, decisions made, and pending items.

Pick up a teammate's open PR in a specific repo, check it out locally, review it, and continue the work. Accepts a repo name (optionally with PR number) as $ARGUMENTS.

Orchestrator agent for the /make-no-mistakes:implement protocol. Executes Linear issues with full discipline: worktree isolation, subagent dispatch for exploration and architecture, all-reviewer loops (Greptile + CodeRabbit + Graphite), CI verification, and clean merges. Dispatched by the implement command to run in its own context window.

Background agent for cross-referencing open PRs with Linear issues, checking Greptile review scores, forcing GitHub mergeable calculation, and generating actionable PR status reports. Dispatched by the review-open-prs skill.

Detects when the user wants to work on a Linear issue, implement a feature, fix a bug, or start development work. Suggests the /make-no-mistakes:implement command. Triggers on: "implement", "work on issue", "start on", "pick up issue", "Linear issue", "build feature", "fix bug", "start coding", "work on ALT-", "work on DOJ-", "implement this", "let's build", "start implementing", "pick up this ticket", "work on this task", "execute this issue", "develop this feature", "ship this", "implement ALT-", "implement DOJ-", pastes a Linear issue URL, or provides an issue ID. Does NOT trigger on: rebase, sync branches, standup, test execution, code review, general coding questions, or session management tasks.

Detects when the user needs to sync branches after a release or rebase their work across multiple branches. Suggests the /make-no-mistakes:rebase command. Triggers on: "sync with release", "rebase all branches", "align with develop", "post-release sync", "branches are behind", "need to rebase everything", "team rebase", "release sync", "sync after merge to main". Does NOT trigger on: single-branch rebase ("rebase this branch"), git rebase interactive, cherry-pick, or simple merge operations.

Reviews active Linear issues with GitHub cross-referencing, activity insights, and actionable recommendations. Use when the user asks "what are my active issues", "review my Linear issues", "what's the status of my issues", "show me my backlog", "what issues need attention", or wants a comprehensive view of their Linear workspace. Do NOT trigger for: creating new issues, PR review, or code implementation.

Cross-references open PRs across all repos in the current org with Linear issues, checks Greptile review scores, forces mergeable calculation, and generates an actionable report with merge/rebase/fix recommendations. Use when the user asks "show me open PRs", "what PRs need attention", "review PRs", "check Greptile scores", "what's ready to merge", or wants a comprehensive PR status overview. Do NOT trigger for: creating PRs, code review, or single PR inspection.

Reads spec files or SRD tasks and produces structured implementation briefs in the Bilingual Format (Human Layer + Agent Layer). Use when the user asks to "analyze this spec", "create an implementation brief", "process this SRD task", "what needs to be built from this spec", or wants to turn a spec document into actionable implementation steps. Supports OpenSpec, numbered steps, and SRD gap audit. Do NOT trigger for: issue analysis (use spike-recommend), code review, or status reports.

Analyzes Linear issues and produces structured bilingual implementation briefs (Human Layer + Agent Layer). Use when the user asks to "analyze this issue", "create an issue brief", "what does this Linear issue need", pastes a Linear issue URL, or wants to understand and plan work for a Linear issue. Do NOT trigger for: general project management, issue creation, or status updates.