workflow-livraison

Validates completed code changes against a five-dimension delivery checklist for the Toollab codebase.

Updated May 5, 2025
One-click install
npx skills add https://github.com/sebauvray/toollab-api --skill workflow-livraison-sebauvray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-livraison
Source: https://github.com/sebauvray/toollab-api/tree/main/.claude/skills/workflow-livraison
Command: npx skills add https://github.com/sebauvray/toollab-api --skill workflow-livraison-sebauvray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unfinished or unsafe work from being declared done by enforcing a mandatory pre-delivery review covering functionality, regressions, security, complexity, and performance before responding to the user. ## Core Features & Use Cases - Five-dimension checklist: Verifies the feature works (golden path and edge cases), no regressions in callers and legacy fallbacks, no security flaws (IDOR, mass assignment, missing auth middleware), justified complexity, and no performance issues (N+1 queries, costly appends). - Codebase-specific checks: Encodes Toollab conventions such as school_id scoping, sanctum middleware, batch UserRole loading, and preserved legacy fields like teacher_name and current_school_role. - Standardized reporting format: Produces a short factual summary of what was done, what was verified, what was not tested, and what was cleaned up. - Use Case: After implementing a new Laravel endpoint and its Nuxt frontend page, invoke this checklist to grep for all callers, confirm middleware coverage, and report exactly which cases were tested before declaring the task complete. ## Quick Start Run the delivery checklist on the work just completed and report what was verified and what remains untested.

Frequently Asked Questions about workflow-livraison

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a feature is complete before delivery?▼

Run the five-dimension checklist: confirm the feature handles golden path and edge cases, review the full git diff for regressions, check security gates on every route, justify complexity, and look for N+1 queries. Report each dimension explicitly in the restitution format.

How to check for regressions after modifying a Laravel controller?▼

Identify all callers of the modified code by grepping the Nuxt services and pages directories for the endpoint or component name. Review the complete git diff of every touched file and confirm legacy fallbacks and existing response formats remain intact.

What security checks should a code review checklist include?▼

Verify IDOR protection on every client-supplied id, never derive school_id from payloads, avoid adding technical fields to fillable arrays, require auth middleware on mutating routes, use generic client error messages, and ensure every catch block logs the error.

When should this delivery checklist be invoked?▼

Invoke it systematically at the end of every implementation, before responding to the user. It is designed as a mandatory gate for the Toollab project, not an optional review, and anything not verified must be declared as untested.

What are the limitations of a checklist-based code review?▼

A checklist cannot execute tests itself; it relies on actually running curl requests, Playwright checks, or test suites for evidence. Cases that cannot be exercised due to environment limits must be explicitly declared as untested rather than assumed correct.