jmlweb

Activate when the project has a .backlog/ directory, or when the user discusses tasks, backlog, ideas, reports, bugs, or learnings. Provides contextual awareness of the flowstate backlog management system.

Generate a Changesets entry and commit it, for Changesets-managed monorepos. Use when the user says "changeset", "add changeset", needs to record a package version bump, or finishes work that should ship in the next release. Detects modified packages from staged files, picks major/minor/patch from the diff, and leaves `changeset version` to CI. Do NOT use for single-package repos or repos without a `.changeset/` directory.

Audit project docs (README, CLAUDE.md, AGENTS.md, package READMEs, docs/) for content drift AND structural fit — versions, commands, paths, examples and instructions out of sync with the code, plus a 3-tier layout check (rules stay terse, READMEs stay human, deep docs live under docs/). Use when the user says "check docs", "are the docs up to date?", after significant code changes, or before a release. Reports content + structural issues; defers markdown style/formatting to a linter. Monorepo-aware.

Create a git commit following Conventional Commits. Use when the user says "commit", "commit these changes", has finished a logical unit of work, or wants to save progress to git. Analyzes the staged diff to infer type/scope, scans for secrets and sensitive files, warns before committing to main/master, and never bypasses hooks without permission.

Review a GitHub pull request with specialized agents running in parallel (code quality, security, QA, architecture as needed). Use when the user says "review PR", "review this pull request", "/review-pr", pastes a GitHub PR URL, or finishes a branch and wants feedback before merge. Fetches diff via `gh`, checks CI status, produces a structured report with risk matrix and merge recommendation. Requires GitHub CLI authenticated.

Document a learning or insight discovered during development. Use when the user says "learned something", "TIL", "note this", "remember this for next time", or when a non-obvious discovery is made while working.

Interactively groom and add a new task to the backlog. Use when the user wants to add work, create a ticket, file a TODO, track a feature request, or says "add task", "new task", "I need to do X".

Verify that a task's declared status matches the actual codebase implementation. Use when the user says "check task status", "verify implementation", or during backlog health checks. Supports single-task and batch mode.

Add a new tradable instrument to the quant universe, or rename/rotate an existing one (VOO→SXR8, GLD→SGLD→4GLD pattern). Covers legality vetting, script wiring, risk classification, docs, and the ticker-alias map. Use when Jose says "add X to the watchlist", "can we trade X", or an instrument changes ticker/listing.

Run the mandatory first-session-of-month documentation and data drift audit — README, ASSETS, RULES, SIGNALS, STRATEGY, dashboard, backtest, language sweep, secrets sweep. Use on the first session of each month, when Jose says "monthly audit", or whenever docs look out of sync with the portfolio.

Diagnose and recover a failed or missing cron trading session (no Telegram received, missing daily file, stale data, failed commit/push, validation failure). Use when a scheduled session (09:00/12:00/15:30/18:00/21:30) didn't complete, when data looks stale, or when Jose says "yesterday's close is missing" or "no telegram arrived".

Release-safety gate for mochila-ts before opening or updating a PR — run the full verify pipeline, classify the diff's real semver impact against the proposed commit/PR title, check the export chain and README table for drift, and produce a ready-to-use PR title and body. Use when the user says "pre-pr", "ready to ship?", "open a PR", "check before merge", or after finishing any branch work.

Add a new utility to mochila-ts end-to-end — scaffold, implement data-last curried function, tests with type-level assertions, wire both export barrels, update the README table script, and run the full verify gate. Use when the user says "add utility", "new function", "implement {name}", or lists several utilities to add.

Adversarial edge-case audit of one or more mochila-ts utilities — hunt the bug classes this library has actually shipped (division by zero, negative-number math, circular references, unicode, memory leaks in stateful utilities), prove each bug with a failing test, then fix. Use when the user says "harden", "audit", "find edge cases", "stress test {utility}", or after a batch of new utilities lands.

Mark an idea as completed when all its derived tasks are done. Note: Ideas are automatically closed when converted to tasks via /feed-backlog. Use this skill only for edge cases (manually created tasks, legacy ideas, etc.).

Evaluate a single idea and decide to accept or reject it. Used internally by /validate-ideas or when the user mentions a specific idea number.