PostToolUse hook that runs Ruff on each edited .py/.pyi file and reports findings to Claude. Claude Code starts only one language server per file extension, so `ruff server` can never run alongside pyright-lsp; this reconstructs the standard Pyright-plus-Ruff split from outside the LSP layer. Read-only: never writes ruff config, never syncs the environment, silent on clean files.
Plugin ruff-diagnostics from marketplace fb-claude-skills in fblissjr/fb-claude-skills. Commands read from the repo's manifest — 10 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
bash
Structured, user-invoked standing prompts for long runs on any project: /design-scoreboard chooses what to climb and what must not get worse, /improve and /optimize climb it against the repo's AGENTS.md sections, and /trim-agents-md keeps that hub short. Each keeps state in files and reports what needs the owner first
4 skills · 2 agents · hooks
MECE decomposition for breaking work into mutually exclusive, collectively exhaustive parts. A skill you invoke when decomposing something -- it ships no SessionStart hook, because the method is needed at a decision point the model can recognise, not before the first action of every session.
5 skills · 1 MCP server
The audit family: evidence-grounded postmortems of finished work with a browsable index, a test-suite audit (does each green test still mean anything), a controls audit (census and live-fire over hooks, validators, and reminders), and the adversarial-verify primitive with its control-builder agent that the audits dispatch to
5 skills · 1 agent
Skills for how the agent writes and explains: an American plain-language house style, voice matching, replacing prose with compact visuals, and re-pitching a message that did not land
4 skills · 1 command
Hand a task to Gemini and get a structured answer back -- video and audio analysis, perceptual image comparison, or any ad-hoc question with model, thinking level, and schema set per call. Explicit, auditable, one run directory per call.
1 skill · 2 commands · hooks
On-demand references for what a repo cannot state by being read: the house Python pinning policy and the two mistakes behind most Pydantic/Pyright diagnostic walls; documentation conventions (last-updated dates, where unshared notes and session logs live, how dependency changes are recorded, no decorative counts in prose); and a uv and bun dependency CVE audit, transitives included. No hooks or ambient injection: conventions belong in each repo's own always-loaded files.
3 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.