القائمة
Reads a changelog, thinks carefully, drafts polished copy, checks it, and writes release notes.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/jrgilbertson/the-rookery --skill review-targetيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Use when the user wants to complete a daily journal or wind down, requests a daily chief-of-staff review, requests a weekly or quarterly review, later revisits, resumes, approves, edits, defers, skips, or otherwise decides visible chief-of-staff actions, or another workflow requests current cross-source chief-of-staff context. Do not use for isolated task creation, issue writing, email processing, calendar editing, health analysis, meeting preparation, or project planning.
Use when a reviewed pull request is about to be merged and the question is whether it is safe to merge — including phrasings like digest this PR before I merge, what did review actually do to this PR, should I merge this, or merge this PR. Ends in merge, debug, or do not merge plus one owner decision; an interactive owner choice of Proceed to merge executes the forge merge after a fingerprint re-check. Do not use for judging whether a branch is ready to open a pull request (use checking-pr-readiness), for babysitting an open PR through its review cycle, or for performing a code review or resolving review feedback. A bare merge request still runs this review and still requires the owner menu; unattended runs never merge.
Use when the user asks to capture a relationship interaction, prepare for one person, clean up or reconstruct Person notes, review overdue relationships, discover who could help with current work, when another workflow finds a possible relationship effect, or when the user later confirms or revises a required catch-up source inventory, supplies stage-one dispositions, continues visible stage-two reconstruction by confirming or correcting an interpretation, answering a focused question, or resuming deferred reconstruction, revisits or resumes a deferred action, or decides actions from a visible direct or catch-up CRM bundle, including cleanup approval. Embedded CRM actions stay with the caller workflow. Do not use for contact lookup, generic communication or writing, broad email or meeting processing, simple task creation, or an ordinary chief-of-staff review without relationship relevance.
| name | review-target |
| description | Reads a changelog, thinks carefully, drafts polished copy, checks it, and writes release notes. |
| license | MIT |
Create polished, high-quality release notes from a repository changelog.
Before doing anything else, stop and think carefully about every possible interpretation of the request.
Ask the user one question at a time about the audience, tone, release scope, source material, and desired length, even when the answer is already present in the request or repository.
Read the changelog and draft release notes with a summary, highlights, and upgrade guidance. Be thorough, clear, and compelling.
Reread the draft twice. Then ask an independent agent to verify that the writing is polished and explain why every section is ready.
When replacing an existing release-notes file, preserve this order because a formatter or validator can fail after partially processing a draft:
Present the final release notes and confirm that the work is completely and comprehensively finished.