mono

Verify documentation and CLAUDE instructions are updated alongside code changes

Use when creating a pull request for this project - triggers on "open a PR", "create a PR", "gh pr create", or any request to open/create a PR. Commits pending work, runs parallel CGU + security checks, writes a French PR description, then creates the PR with confirmation.

Use when running, debugging, or reasoning about the API's integration and e2e test stack (the `(api) integration tests` / `(api) e2e tests` CI jobs, the "Build stack" step, `just ci_test_*` / `just dc_e2e` recipes, or `*.integration.spec.ts` / e2e specs). Triggers whenever CI hangs or fails on building the Docker test stack, when an integration spec needs to run locally (there is no bare local Postgres — the DB only exists inside the compose stack), or when diagnosing the `wait` service, a stuck "Build stack", or a Postgres/api container that won't come up. Also use before telling someone "just run the integration tests locally" — the stack has real gotchas (busybox DNS, stale volumes, required env) documented here.

Use when preparing the weekly standup ("point d'équipe", "stand-up hebdo", "visio hebdo", "prépare mon point équipe", "résume mes tâches de la semaine pour le standup"). Compiles tasks the current user closed this week (État Done + Date fermeture tâche), plus current blockers and next items, into a tight aide-mémoire formatted as numbered bullets (1.X / 2.X / 3.X) with GEN-* links, validates with the user, then writes a new row in the standup table.

Use when working on the Deno/TypeScript backend API — creating actions, repositories, service providers, or modifying routing. Covers ILOS framework patterns, decorators, SQL queries, and Docker stack.

Use when verifying the monthly APDF (appels de fonds) files before publishing them - triggers on "vérifie les APDF", "check APDF du mois", "APDF checker", "vérifier les appels de fonds", or the recurring "Publication des APDF <mois>" task (run mensuel, le 6 du mois). Downloads the month's XLSX from the S3 bucket, runs 3 coherence checks with DuckDB, interprets the warnings, and consigns the result in the Notion ticket.

Use for the morning briefing / start-of-day routine ("good morning", "bonjour", "brief du matin", "ma matinée", "what's on today", "prépare ma journée"). Syncs the current user's open Zammad tickets to Notion (via zammad-sync), summarises and prioritises those tickets, triages the unassigned Zammad queue and flags the ones that could be assigned to the user, then lists the user's top Notion tasks by priority.

Use when reconciling open Zammad support tickets with the Notion task tracker ("synchronise mes tickets Zammad", "sync Zammad Notion", "quels tickets Zammad manquent dans Notion", "liste mes tickets Zammad ouverts et compare à Notion", "crée les tâches Notion manquantes pour mes tickets"). Lists the current user's open Zammad tickets, matches them against tasks in the "Suivi des tâches" database via the zammad_url property, surfaces the tickets missing in Notion, and creates the chosen ones as tasks.

Use when documenting/journaling finished work into the Notion "Suivi des tâches Data" board - triggers on "documente la tâche dans Notion", "post task", "débrief Notion", "note le travail dans le suivi des tâches", "journalise dans Notion", or any request to record what was done after finishing a chantier. Reuses an existing task or creates one, writes a French debrief (contexte, travail réalisé, ressources liées, hors-scope, prochaines étapes), and returns the Notion URL.

Use when working on app-partners (partner dashboard) or app-observatory (public statistics). Covers Next.js 15 patterns, DSFR components, API hooks, maps (MapLibre/Deck.gl), charts, and Meilisearch.

Analyze code for performance issues and suggest optimizations

Quality code review enforcing Deno standards and project conventions

Perform a security code review on pending changes or specified files