القائمة
Describes how to use abilities. Read before any conversation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Check papers/ structure for completeness and accuracy — every PDF has text extraction, every paper is indexed in PAPER_INDEX.md and summarized in PAPER_SUMMARIES.md, summaries are factually accurate. Prompts the user for discrepancies.
Use when you want to clean up accumulated git worktrees in a repo. Lists all worktrees with status, verifies data symlinks, ensures code and docs are committed, copies non-symlinked data files to main worktree, asks which to merge or keep, runs post-merge audits on new docs/papers, and removes merged worktrees.
Use after creating or modifying decision documents in docs/ to keep DOCS_INDEX.md and DOCS_SUMMARY.md consistent. Also use as a standalone audit to find coverage gaps, broken links, and ADR format issues. Works across any repo with a docs/ directory. Run alongside updating-noridocs when finishing a branch that includes decision docs.
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
End a research session — runs update-docs to checkpoint all progress, then commits and pushes. Use update-docs for mid-session checkpoints without ending the session.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
استنادا إلى تصنيف SOC المهني
| name | Getting Started with Abilities |
| description | Describes how to use abilities. Read before any conversation. |
After you've read a ability with Read tool, announce you're using it:
"I've read the [Skill Name] ability and I'm using it to [what you're doing]."
Examples:
Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the ability.
Many abilities contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.
Some abilities are flexible patterns (architecture, naming). Adapt core principles to your context.
The ability itself tells you which type it is.
