baume

Discover all OpenAPI specifications in the codebase. Outputs a discovery document listing all found specs with metadata.

Apply fixes to OpenAPI specs. Two modes available:

Create a prioritized fix plan from API review findings. Groups related issues, finds code locations, and suggests implementation order with both spec and code diffs.

Analyze an OpenAPI specification against API best practices using the deterministic JS reviewer.

Validate fixes by re-running review and comparing against the plan. Updates plan status and shows remaining issues.

Find code that implements a single API operation. This agent should be used when mapping API findings to code locations, or when the user asks where an API endpoint is implemented. Spawn multiple instances in parallel for speed when locating multiple operations. <example> Context: User wants to fix an API finding and needs to know where the code is user: "Where is the GET /users/{id} endpoint implemented?" assistant: "I'll use the baume-code-locator agent to find the controller or route handler for that endpoint." <commentary> User needs to locate specific API implementation code - use baume-code-locator. </commentary> </example> <example> Context: Creating a fix plan that requires code changes user: "Find all the code locations for the endpoints in this review" assistant: "I'll spawn baume-code-locator agents in parallel for each operation to find all code locations." <commentary> Multiple endpoints need code location - spawn multiple baume-code-locator agents in parallel. </commentary> </example>

Fetch and explain specific API rules (e.g. Google API Improvement Proposals (AIPs)). This agent should be used when the user asks "why" about an API rule, wants to understand a specific rule identifier (e.g.AIP number), or needs detailed guidance on API design patterns. <example> Context: User received a Baume review finding about naming conventions user: "Why does the review say I need plural resource names?" assistant: "Let me look up AIP-122 to explain the rationale for plural resource names." <commentary> User is asking "why" about an API rule - use baume-lookup to fetch and explain the specific API rule. </commentary> </example> <example> Context: User is designing a new API endpoint user: "What's the proper way to do pagination according to Google's guidelines?" assistant: "I'll fetch AIP-158 to explain the pagination requirements and best practices." <commentary> User wants detailed guidance on a specific API pattern - use baume-lookup to provide authoritative AIP guidance. </commentary> </example> <example> Context: User sees an error-related finding in their review user: "Tell me more about AIP-193" assistant: "Let me fetch AIP-193 to explain the error handling standards." <commentary> User explicitly asks about a specific API rule - use baume-lookup agent. </commentary> </example>

This skill should be used when the user asks about "AIP rules", "API Improvement Proposals", "Google API guidelines", "AIP-158", "AIP-193", or any specific AIP number. Also use when user asks "how should I implement pagination", "what's the right error format", "how do I design a REST API following Google's standards", or needs guidance on errors, pagination, filtering, field masks, long-running operations, or batch operations in REST/OpenAPI APIs.

This skill should be used when the user asks "where is this API endpoint implemented", "find the code for this route", "which file handles this endpoint", "map API findings to code", or needs to correlate OpenAPI spec paths with source code locations. Also use when creating fix plans for code-first API projects (NestJS, Fastify, Express) after running baume-review, or when user mentions "find my NestJS controller", "locate Fastify route handler", "Express route definition".

1 hook across 1 event

Baume API Hygiene Coach - provides tools for reviewing OpenAPI specs against API best practices