Read-only reviewer for JWT login, password hashing, and /auth routes in this tracker. Use when the user asks to review auth.py, registration, login tokens, or getcurrentuser. Use after changes to auth helpers or auth routes. Do not use for session/cost exploration or for implementing features.
General-purpose code reviewer for single files or focused diffs. Use when reviewing specific files or a single diff before merging. Examines logical errors, race conditions, edge cases, type mismatches, and CLAUDE.md compliance. Reports issues by severity with file:line references. For multi-file PR or pre-merge…
MUST BE USED for finding code usages and building usage maps. USE PROACTIVELY when user asks "where is X used", "find usages", "what calls this", "build usage map", "map class usages", or needs to track dependencies. Expert at finding functions, methods, classes, variables across codebases and generating structured…
Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, B2 English. Saves saifcoverletter.tex to the output folder.
Use for systematic investigation of bugs, test failures, or runtime errors. Reproduces first, then forms 2-3 ranked hypotheses with evidence, investigates code paths and git history, and proposes the minimal fix. Never guesses; never shotgun-debugs. Returns a single report — does not modify code.
Reads the turns a session has had since it last ran, searches the memai store, and reports only the memories that bear on what is actually happening -- a pitfall the work is walking into, a decision it is about to contradict, a fact it is about to rediscover. Launched by the session itself when the Stop hook says the…
★not rated 0 5d agoA96 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: