antoine-bouteiller

Diagnose and fix a failing SonarQube quality gate on the current branch's merge request — resolves the project + PR, reads the failing conditions, then fixes new violations and coverage gaps. Use when the user says "fix the sonarqube gate", "the sonar quality gate is failing", or after a pipeline reports a red SonarQube check.

Generate conventional commit with staged changes

Review a merge request for security, performance, architecture, style, and improvements

Research a task and write a phased plan to .plan/<slug>.md without implementing it. Use when the user wants to plan a feature or change before building, asks to "make a plan", or when a task is large enough to design before touching code. Replaces built-in plan mode.

Explore several design solutions for a task and compare their trade-offs without implementing anything. Use when the user wants to weigh approaches before committing, asks to "explore options", "compare designs", or "what are my options" for a change.

Implement a piece of work based on a spec or set of tickets.

Create unpublished inline DRAFT review comments on a GitLab merge request diff via the GitLab API. Use when a code review has produced findings that should be attached to exact diff lines as drafts (not published) so the human can review and submit them in one batch. Carries a ready-to-post dataset for Phoenix MR !145 (View360 view-based rework).

Update a GitLab merge request's title + description and the Linear ticket linked to it, auto-discovering both from the current git branch. Use when the user asks to "update the MR", "update the MR and ticket", "sync the MR description", or after rewriting commits / finishing a feature. The MR is found by branch (never assume the !N), and the Linear ticket key is derived from the branch name (e.g. phx-118-… → PHX-118).

Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Invoke for Entity Framework Core, minimal APIs, async patterns, CQRS with MediatR.

Common Python anti-patterns to avoid. Use as a checklist when reviewing code, before finalizing implementations, or when debugging issues that might stem from known bad practices.

Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

Use when building Python 3.11+ applications requiring type safety, async programming, or production-grade patterns. Invoke for type hints, pytest, async/await, dataclasses, mypy configuration.

Python type safety with type hints, generics, protocols, and strict type checking. Use when adding type annotations, implementing generic classes, defining structural interfaces, or configuring mypy/pyright.