Operate the Graphite Merge Queue — enqueue PRs via label, dequeue, monitor queue status, and reason about stacked-PR queueing. Use when the user mentions Graphite merge queue, "merge when ready", queueing a PR, dequeueing, fast-track, the merge-queue label, "enqueue", "the queue", or when they ask to merge a PR/stack through Graphite (not directly). Triggers on phrases like "queue this PR", "add to merge queue", "enqueue stack", "remove from queue", "why didn't my PR merge", and on edits to `.please/config.yml` under `graphite.merge-queue`.

Configure a GitHub repository for Graphite — branch protection, merge queue, CI triggers, and stack-aware CI optimizations. Use when the user is onboarding a repo to Graphite, mentions Graphite branch protection / required checks / signed commits / merge queue, sees CI failing on `graphite-base/*` branches, asks about merge-queue choice (Graphite vs GitHub vs external), or wants to reduce CI cost for stacked PRs (CI Optimizations, stack-aware CI, `needs.optimize_ci.outputs.skip`). Triggers on `.github/workflows/*.yml` changes for repos using Graphite, the phrases "stack CI", "stacking and CI", "graphite-base", and any branch-protection or merge-queue discussion in a Graphite repo.

Drive the Graphite CLI (`gt`) for stacked pull-request workflows. Use when the user works with stacked PRs, mentions Graphite, gt, "the stack", or wants to create/submit/sync/restack/split/squash/fold branches. Triggers on `gt` commands, "stack of PRs", "stacked diffs", "trunk-based", `.graphite_repo_config`, branches prefixed by a Graphite user (e.g. `lms--`, `pp--`).

Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.

Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

Use when a learner wants to start, work through, or be guided or tutored through the Your first code review lesson, the opening lesson of the Code Review Loops course. Walks them one step at a time through scaffolding a small service with a deliberately flawed branch, running a Tessl Code Review over it three different ways, and reading the outcome, the severities and the JSON result, checking what they got after each step before moving on. Triggers on asks like guide me through your first code review, start the code review course, how do I run tessl code review, or review my branch with Tessl.

Use when a learner wants to start, work through, or be guided or tutored through the Writing a review lens lesson from the Code Review Loops course. Walks them one step at a time through authoring a review lens that encodes one of their own team's conventions, running it beside pinned default lenses, and testing it in both directions so it fires on the bad case and stays quiet on the good one. Triggers on asks like guide me through writing a review lens, how do I write a custom code review lens, make Tessl check my team's conventions, or create a lens for tessl code review.

Use when a learner wants to start, work through, or be guided or tutored through the Routing lenses by path lesson from the Code Review Loops course. Walks them one step at a time through writing a repository YAML review profile, scoping each lens to the paths its rule governs with globs and exclusions, proving the routing in both directions, and understanding why a skipped review must never be read as an approval. Triggers on asks like guide me through routing lenses by path, how do I write a tessl-code-review.yml, scope a review lens to certain files, or what does no-matching-lenses mean.