菜单
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.
用 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.
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.
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 | workflow-guidance |
| description | 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. |
A conversation, not a race. Start by understanding the problem — ask questions, challenge assumptions. Don't call ExitPlanMode until explicitly given the green light. Enter plan mode for architectural decisions or non-obvious tradeoffs.
.claude/rules/lessons.md
(project-level only; ~/.claude/rules/lessons.md is user-curated).Save to .claude/plans/. Use system-assigned filenames as-is.
Plan → verify → track → explain → capture lessons.
Subject ≤72 chars; body explains why. Never "update", "fix bug", "WIP", "changes".
No Co-Authored-By: trailers — commits are authored solely by the user.