القائمة
Org-mode todo.org conventions for project task tracking. Use when the user pastes a `** TODO` heading, asks about project TODOs or plans, or when deciding where to track tasks or mark work complete.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Acid Genomics R package development conventions — per-project air.toml, global ~/.lintr only, roxygen2 8.x @importFrom split, S4 linter tuning, AcidDevTools::check() gate. Use when writing or checking an acidgenomics R package, configuring air/lintr, or fixing roxygen/lint failures.
Diagnose and recover from common git branch/state accidents — wrong-branch reset, git alias side effects, untracked-file checkout collisions, and stash cleanup. Use when a git command moved the wrong branch pointer, a checkout was blocked by untracked files, or stash noise is showing in the prompt.
Guide for maintaining and optimizing Claude Code configuration — CLAUDE.md, rules files, hooks, and skills. Use when auditing instruction bloat, deciding where a new rule belongs, or pruning stale content.
Workflow orchestration guidance — plan mode etiquette, subagent discipline, session hygiene, and git commit conventions. Use when asked about plan mode, how to structure multi-step work, when to use subagents, or when making a git commit.
Claude Code permission system internals — protected paths, permission modes, allow/ask/deny rule precedence, and the PreToolUse permissionDecision hook contract. Use when debugging unexpected permission prompts, understanding why Edit(.claude/**) or Bash(*) allow rules have no effect on .claude/ writes, or reasoning about acceptEdits vs plan vs bypassPermissions mode tradeoffs.
Rewrite git history safely with git filter-repo. Use when removing secrets or sensitive files from commits, rewriting author/committer emails across history, de-duplicating doubled commits, or any commit-level surgery.
| name | todo-org |
| description | Org-mode todo.org conventions for project task tracking. Use when the user pastes a `** TODO` heading, asks about project TODOs or plans, or when deciding where to track tasks or mark work complete. |
** TODO heading is pastedtodo.org at the project repo root (not .claude/todo.md or
anywhere else — the repo root only).** TODO — open task** DONE — completed and verifiedMark an entry ** DONE only when the work is verified complete — not on a
plausible-looking diff alone.
* Category heading
** TODO Short task title
Optional note line(s), indented with spaces.
https://link-to-issue-or-reference
** DONE Completed task title
Heading depth is two stars (**) for tasks under a category. The file lives at
the repo root and is committed alongside code.
CLAUDE.md in the koopa repo explicitly states: plans/TODOs → todo.org at the
repo root, NOT .claude/todo.md. This skill generalizes that convention to any
project that follows the same pattern.