القائمة
Build and maintain a persistent graph of architecture, conventions, bug history, ownership patterns, and module relationships for this specific codebase.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Optimize token usage and context window discipline. Reduce costs and improve response quality through smart context management.
Unified context lifecycle for FlowDeck sessions — ingest, filter, prune, protect, summarize, and persist with telemetry.
Predict affected files, modules, APIs, tests, and DB paths before changes. Returns an impact map for human review.
Map architecture, conventions, and file structure into `.codebase/`. Use when onboarding or before deep feature work.
Plan differently when the agent has low certainty — ask for clarification or narrow scope instead of pretending full understanding.
Protect critical context from pruning during compaction. Preserve active plans, safety files, pending operations, and user intent anchors.
| name | repo-memory-graph |
| description | Build and maintain a persistent graph of architecture, conventions, bug history, ownership patterns, and module relationships for this specific codebase. |
| origin | FlowDeck |
The Repo Memory Graph is FlowDeck's long-term knowledge store about this specific codebase. It persists in .codebase/MEMORY.json and grows over time.
Update the graph:
/fd-task maps the codebase during initbug_history)repo-memory tool// Write a node
{ "action": "write_node", "node_id": "auth-service", "node": {
"type": "service", "path": "src/services/auth.ts",
"owner": "security-team", "tags": ["auth", "jwt"],
"dependencies": ["user-model", "token-store"],
"dependents": ["api-gateway", "session-handler"],
"bug_history": ["jwt-expiry-bug-2024-03"],
"conventions": ["always validate token before processing"]
}}
// Query by owner
{ "action": "query", "query": { "owner": "security-team" } }