القائمة
Analyzes commit history, PR descriptions, and spec changes to automatically generate developer-friendly API changelogs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create, optimize, critique, and programmatically structure prompts for AI systems. Use this skill whenever the user is designing or improving a static prompt, system prompt, coding prompt, agent prompt, workflow prompt, MCP-oriented prompt package, or an algorithmic prompt optimization pipeline. Also use it when the user asks to turn vague AI behavior into a precise instruction set, tool policy, agent spec, evaluation metric, or prompt architecture.
Enforce and manage DESIGN.md specifications, extract design systems from URLs, and combine design reasoning with token roles to prevent drift.
Assumption-first architecture review skill to stress-test project plans and expose hidden risks.
Forces the agent to act with a Claude-like product mindset, prioritizing user journey, UX states, and visual quality before coding.
Compiles and extracts session knowledge into a living, interconnected LLM-Wiki. Instead of writing isolated logs, it identifies key entities, updates cross-referenced topic files in docs/knowledgelib/, and maintains an index and chronological log. Use this to ensure persistent, compounding project knowledge.
Overrides the agent's behavior to enter an interactive, consulting mode. Instead of guessing or immediately executing a task, the agent will analyze the request and ask guiding, targeted questions to clarify intent, constraints, and requirements first.
| name | changelog-generator |
| description | Analyzes commit history, PR descriptions, and spec changes to automatically generate developer-friendly API changelogs. |
This skill bridges the gap between raw git history and consumer-facing API updates. Consumers don't care about "Refactored user service;" they care about "The /users endpoint now returns a profile_pic URL."
Core assumption: A changelog is a communication tool, not a git dump. It must focus on the API interface, not internal implementation tweaks.
Parse the provided text (Git commits, PR bodies, or OpenAPI diffs) and filter out internal noise.
Organize the update into established categories:
breaking-change-detector).Required Outputs (Must write BOTH to docs/api-report/):
docs/api-report/api-changelog.md)# 🌍 API Changelog
## [v1.4.0] - 2024-03-24
### 🚀 Features
- **[Orders]** Added new `POST /v1/orders/{id}/cancel` endpoint. You can now cancel orders within 30 minutes of creation.
- **[Users]** The `GET /v1/users/me` endpoint now includes a `last_login_at` timestamp.
### 🛠️ Fixes
- **[Payments]** Fixed an issue where `GET /v1/payments` would return a 500 error if the user had no payment methods. It now correctly returns an empty array `[]`.
### ⚠️ Deprecations
- **[Products]** The `category_id` field in the `/products` response is deprecated. Please use the new `categories` array instead. `category_id` will be removed in v2.0.0.
docs/api-report/api-changelog-output.json){
"skill": "changelog-generator",
"version": "1.4.0",
"date": "2024-03-24",
"changes": {
"features": ["POST /v1/orders/{id}/cancel added", "last_login_at added to GET /v1/users/me"],
"fixes": ["GET /v1/payments empty state fix"],
"deprecations": ["category_id in /products response"]
},
"breaking_changes": []
}