القائمة
Review and update .claude/ configuration to reflect the current state of the project. Use after adding new domains, patterns, conventions, or when the user corrects an approach.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Add a complete REST endpoint from command to controller route. Use when building new API endpoints.
Summarize the API interface changes made during THIS session for the frontend, then optionally spawn an agent to implement them in the frontend repo. Use after changing endpoints, request/response DTOs, or auth.
One-shot guided session — prunes unused code, scaffolds new entities/endpoints, updates project identity config, and replaces the init migration for a specific project.
Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"
Implement a change with a pipeline scaled to its complexity. Single entry point for all code changes — auto-detects effort or accepts small|mid|tuff override.
Run a Linear task end-to-end — creates an isolated tmux session + worktree, starts a Claude agent to implement it, opens a PR, and watches for review feedback automatically.
| name | update-knowledge |
| description | Review and update .claude/ configuration to reflect the current state of the project. Use after adding new domains, patterns, conventions, or when the user corrects an approach. |
| argument-hint | ["topic"] |
Review the .claude/ configuration against the actual codebase and propose updates.
$0 (optional) -- Specific topic to update (e.g., "new payment domain", "error handling convention"). If omitted, do a full review.Current entities:
!find backend/domain/entities -name "*.py" -not -name "__init__.py" -not -path "*base*" -not -path "*__pycache__*" 2>/dev/null | sort
Current handlers:
!find backend/app/rest/v1/handlers -mindepth 2 -name "*.py" -not -name "__init__.py" -not -path "*base*" -not -path "*__pycache__*" 2>/dev/null | sort
Current ports:
!find backend/app/shared/ports -name "*.py" -not -name "__init__.py" -not -path "*__pycache__*" 2>/dev/null | sort
Current events:
!find backend/app/shared/events -name "*.py" -not -name "__init__.py" -not -name "base.py" -not -path "*__pycache__*" 2>/dev/null | sort
Current controllers:
!find backend/entry/rest/v1 -maxdepth 1 -name "*.py" -not -name "__init__.py" -not -path "*__pycache__*" 2>/dev/null | sort
Recent git changes:
!git log --oneline -15 2>/dev/null
Read each of these and check if they're still accurate:
.claude/CLAUDE.md — does the architecture section match reality? Any new patterns?.claude/rules/*.md — do code examples still match current code? Any new conventions?.claude/skills/*/SKILL.md — do the !find commands reflect current structure? Any new skill needed?.claude/agents/*.md — do review checklists cover all current patterns?For each gap found, categorize it:
For each update, present:
### Update: {file path}
**Why**: {what changed and why the docs need updating}
**Current** (line N):
> {current text}
**Proposed**:
> {new text}
After the user approves, update the files. For each change: