postman-collections

Synchronize Postman collections with current API endpoints and validation rules.

Updated Aug 15, 2025

Search Tags:#openapi #environment variables #postman #api synchronization #request examples #collection import #endpoint diffs

Ready to run

npx skills add https://github.com/pekral/pekral.cz --skill postman-collections

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postman-collections
Source: https://github.com/pekral/pekral.cz/tree/main/.claude/skills/postman-collections
Command: npx skills add https://github.com/pekral/pekral.cz --skill postman-collections

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents Postman collections from drifting away from your real API routes, schemas, and validation rules, so requests stay importable and work reliably after endpoint changes.

Core Features & Use Cases

Detect endpoint changes from the current diff against route/config/schema sources and group updates by resource (e.g., Users, Orders, Auth).
Generate or update Postman collections by creating missing collections or updating existing ones, keeping method + path, headers, auth variables, and request/response examples aligned.
Harden safety and operability by keeping secrets out via environment variables, removing stale endpoints, validating Postman JSON shape, and ensuring the collection can be imported and run.

Quick Start

Use the postman-collections skill to update (or create) Postman collection files and the environment placeholders so they match the latest backend endpoint changes.

Frequently Asked Questions about postman-collections

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

FAQPage Schema

How do I keep Postman collections in sync with API endpoint changes?▼

Synchronizing Postman collections with API endpoint changes involves detecting route, method, and schema modifications from your codebase diff, then updating collection files and environment variables to ensure requests remain importable and runnable.

How does API synchronization handle stale requests and updated validation rules?▼

API synchronization detects modified routes, headers, and request body shapes, then updates the Postman collection JSON by removing stale endpoints and aligning request and response examples with current validation rules.

What is the best way to generate Postman collections from Laravel-style routes?▼

Generating Postman collections from Laravel-style routes requires parsing route/controller schemas and API docs, grouping updates by resource, and creating valid Postman v2.1 JSON with auth placeholders and environment variables.

Can I use environment variables for auth placeholders when importing Postman collections?▼

Yes, you can use environment variables for auth placeholders during Postman collection import. This keeps secrets out of the collection files by injecting baseUrl and authentication tokens dynamically at runtime.

Does Postman v2.1 JSON validation prevent broken collection imports after endpoint diffs?▼

Validating Postman v2.1 JSON schema ensures collection importability after endpoint diffs by verifying the JSON shape, confirming runnable behavior, and removing stale requests before finalizing the import process.

Why should I group API endpoint updates by resource when synchronizing Postman?▼

Grouping API endpoint updates by resource, such as Users or Orders, during Postman synchronization organizes request modifications logically, making collections easier to navigate and maintain across large API surfaces.