القائمة
Best practices for session documentation - incremental summaries, fix reports, and audit trails
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run shell commands bare — no decorative echo headers ("=== X ==="), no echo-then-cmd chains, no trailing "echo done". Use the Bash tool's description field for any narration. Triggers any time you're about to issue a Bash command.
Expert guide for managing Claude Code global skills and commands. Use when creating new skills, symlinking to projects, updating existing skills, or organizing the centralized skill repository.
Token optimization best practices for cost-effective Claude Code usage. Automatically applies efficient file reading, command execution, and output handling strategies. Includes model selection guidance (Opus for learning, Sonnet for development/debugging). Prefers bash commands over reading files.
BioBlend and Planemo expertise for Galaxy workflow automation. Galaxy API usage, workflow invocation, status checking, error handling, batch processing, and dataset management. Essential for any Galaxy automation project.
Expert in Galaxy tool wrapper development, XML schemas, Planemo testing, and best practices for creating Galaxy tools
Expert in Galaxy workflow development, testing, and IWC best practices. Create, validate, and optimize .ga workflows following Intergalactic Workflow Commission standards.
| name | documentation |
| description | Best practices for session documentation - incremental summaries, fix reports, and audit trails |
| allowed-tools | Read, Grep, Glob, Bash |
Best practices for creating effective documentation during Claude Code sessions.
When working through multiple related issues in a session:
Create summary after each major fix:
FIX_SUMMARY.md - First issue resolvedFISH_CLASSIFICATION_FIX_SUMMARY.md - Second issueTAXONOMY_COMPLETE_SUMMARY.md - Final stateBenefits:
Include in each summary:
# [Issue Name] - [STATUS]
## Problem
[Clear description of what was wrong]
## Root Cause
[Why the problem occurred]
## Items Fixed (N total)
| Item | Details | Category |
|------|---------|----------|
| ... | ... | ... |
## Solution Applied
1. [Step 1]
2. [Step 2]
...
## Verification Results
✓ [What was verified]
✓ [Counts match]
## Files Modified
1. `file1.txt` - [what changed]
2. `file2.txt` - [what changed]
## Next Steps
[What the user should do now]
Use descriptive names that indicate:
FISH_CLASSIFICATION_FIX_SUMMARY.mdTAXONOMY_COMPLETE_SUMMARY.mdAvoid generic names like SUMMARY.md or NOTES.md.