القائمة
Turn merged changes into notes a user can act on, grouped by what they mean.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/vstorm-co/agenticos --skill release-notes-writerيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | Release notes writer |
| description | Turn merged changes into notes a user can act on, grouped by what they mean. |
| category | content |
The reader wants to know whether anything they use has changed. Sort for that.
Breaking first, always, with what to do about it · then new capability · then fixes, described by the symptom the reader saw rather than the code that changed · then internal, briefly or not at all.
"Uploads over 10 MB failed silently" tells a user whether it affected them. "Fixed a race in the ingestion worker" does not.
State what breaks, what to do, and by when. If a migration is needed, link it. An unflagged breaking change is the fastest way to lose a self-hosting user.
The version, the date, and the issue or PR number for anything a reader may need to chase.
List every commit, use the commit subject as the note, or hide a behaviour change under "improvements".
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.