# Agent Mode Queries API Catalog and Fixes Spec Issues Source: https://www.youtube.com/watch?v=y18A3AUc80Y Recap page: https://rapidrecap.app/video/y18A3AUc80Y Generated: 2026-02-26T00:37:42.464+00:00 --- ## Quick Overview The agent mode successfully resolved 30 lint warnings in the user-permissions OpenAPI specification by generating a fixed YAML file, updating the corresponding Postman collection structure, and validating the fix by running API tests which passed successfully. **Key Points:** - The agent mode fixed 30 lint warnings identified in the user-permissions OpenAPI spec (user_permissions.api.yaml), which were causing governance compliance issues. - The fix involved generating a complete fixed YAML file which was then used to update the Postman collection structure (User Permissions API.postman_collection.json). - The user requested fixes for lint warnings and updates to the backend code (server.js) and collection structure. - The quality summary showed an 'Excellent' overall score (A) before the process, with governance issues stemming from the lint warnings. - After updating the spec and collection, Postman API tests were run, showing success across all steps, including 'Lint API Specification', confirming the fixes. - The speaker noted that the documentation was updated to reflect changes like removing an endpoint and updating response formats. - The process concluded with committing the changes to the GitHub repository and closing the associated pull request. ![Screenshot at 00:13: The Quality Summary panel displaying an 'Excellent' Overall Quality Score of 'A' for the user-permissions service, immediately followed by listing specific Quality Dimensions like 'Governance' showing 'Minor issues' related to 30 lint warnings.](https://ss.rapidrecap.app/screens/y18A3AUc80Y/00-00-13.jpg) **Context:** The video demonstrates the use of an AI agent (Claude Opus 4.5) in a development workflow to address quality issues identified in an API specification (OpenAPI/YAML) for a service named 'user-permissions'. The initial quality check highlighted 30 lint warnings related to governance best practices, which the agent was tasked to resolve by fixing the specification and updating related assets like a Postman collection. ## Detailed Analysis The demonstration begins by examining the Quality Summary for the 'user-permissions' service, which achieved an 'Excellent' score (A) but flagged 30 lint warnings in the spec file (user_permissions.api.yaml) as an area of concern impacting API governance best practices. The user prompts the agent to fix these 30 lint warnings. The agent first generates the complete fixed YAML file, detailing exactly which lines were changed to resolve the warnings, such as updating inline schemas to use reusable components (e.g., resolving issues on lines 147, 178, 185, 190, 209, 210). The agent then updates the Postman collection by suggesting the user update their local collection file to match the fixed spec. The agent also updates the backend (server.js) to align with the updated specification, including changes to endpoint handling, response formats, and removing an obsolete endpoint. Finally, the user commits these changes to the 'simple-spec-linting' branch, merges the pull request, and runs the Postman API tests in the CI pipeline. The CI run, which includes a 'Lint API Specification' step, shows success with 'No issues found', confirming the agent's fixes resolved the initial governance warnings. ### Service Health Overview - Overall Quality Score is A (Excellent) - Governance dimension shows Minor Issues due to 30 lint warnings - Performance is Excellent (4ms avg. time p95). ### Areas of Concern - 30 Lint Warnings accumulated in user_permissions.api.yaml - No Mock Server configured - No Environments configured - 2 Open PRs pending. ### Agent Action - User requests fixing the 30 lint warnings in user_permissions.api.yaml - Agent generates a fixed spec detailing 10 resolved lint warnings shown in a diff view. ### Postman Collection Update - Agent updates the Postman collection structure to match the fixed spec, resulting in 3 folders (Users, User Permissions, Permissions) and the collection matching the updated spec. ### Backend Synchronization - Agent updates server.js to reflect spec changes, including updating data structures and response formats. ### Validation and Conclusion - Merging the PR and running CI/CD pipeline confirms success, as the 'Lint API Specification' step reports 'No issues found', and the Postman tests pass. ![Screenshot at 00:00: The initial view showing the CI/CD Activity dashboard for the 'user-permissions' service, highlighting the open pull requests and the agent chat interface.](https://ss.rapidrecap.app/screens/y18A3AUc80Y/00-00-00.jpg) ![Screenshot at 00:13: The Quality Summary panel displaying an 'Excellent' Overall Quality Score of 'A' for the user-permissions service, immediately followed by listing specific Quality Dimensions like 'Governance' showing 'Minor issues' related to 30 lint warnings.](https://ss.rapidrecap.app/screens/y18A3AUc80Y/00-00-13.jpg) ![Screenshot at 01:18: The agent output showing 'What This Fixed Version Includes,' detailing the original issues \(line numbers and error types\) and the corresponding fixes applied to resolve all 10 lint warnings shown in that view.](https://ss.rapidrecap.app/screens/y18A3AUc80Y/00-01-18.jpg) ![Screenshot at 02:52: The Postman application interface showing the structure of the User Permissions API collection, organized into 'Users', 'User Permissions', and 'Permissions' folders, which was updated based on the fixed spec.](https://ss.rapidrecap.app/screens/y18A3AUc80Y/00-02-52.jpg) ![Screenshot at 03:34: The GitHub Pull Request screen showing the merged status and the successful CI run, with the 'Lint API Specification' step showing zero issues found.](https://ss.rapidrecap.app/screens/y18A3AUc80Y/00-03-34.jpg)