القائمة
Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/backnotprop/plannotator --skill plannotator-lastيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing. Also trigger when the user says things like "let's ship", "prep a release", "what's changed since last release", or "time to cut a new version".
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | plannotator-last |
| description | Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue. |
| disable-model-invocation | true |
Use this skill when the user wants to annotate the latest assistant response in Plannotator.
Do not send a commentary/status message before running the command. The command targets the latest rendered assistant response, so a preamble can mistakenly become the thing being annotated.
Run:
plannotator last
Behavior:
"decision": "approved" result with a
"feedback" field. Read those notes and carry them into subsequent work, but
do not redo the message over them: they are guidance, not a change request.Run the command yourself rather than telling the user to invoke shell syntax manually.