Skip to content

AGENTS.md

Latest commit

 

History

History
122 lines (84 loc) · 3.13 KB

AGENTS.md

File metadata and controls

122 lines (84 loc) · 3.13 KB
Raw

Grite

This repository uses Grite as the canonical task and memory system. Always use grite commands (not git) for task/issue tracking.

When to use grite

  • "What tasks are done/open?" → grite issue list
  • "What did I work on?" → grite issue list --state closed
  • "What do I know about X?" → grite issue list --label memory
  • "What should I work on next?" → grite issue dep topo --state open
  • "What does function X do?" → grite context query X
  • Starting a new task → grite issue create
  • Making progress → grite issue comment
  • Task A depends on B → grite issue dep add

Startup routine

Run at the beginning of each session:

grite sync --pull --json
grite issue list --json
grite issue dep topo --state open --json

Creating tasks/memories

# Create a task
grite issue create --title "Task title" --body "Description" --label agent:todo --json

# Store a discovery as memory
grite issue create --title "[Memory] Topic" --body "What you learned..." --label memory --json

Working on issues

# Add a comment with your plan before coding
grite issue comment <ID> --body "Plan: ..." --json

# Add checkpoint comments after milestones
grite issue comment <ID> --body "Checkpoint: what changed, why, tests run" --json

# Close when done
grite issue close <ID> --json
grite sync --push --json

Querying tasks

# All issues
grite issue list --json

# Open tasks
grite issue list --state open --json

# Completed tasks
grite issue list --state closed --json

# Memories
grite issue list --label memory --json

Dependencies

Track task ordering and blockers with a dependency DAG:

# Task A depends on Task B (B must complete first)
grite issue dep add <A> --target <B> --type depends_on --json

# Task A blocks Task B (A must complete first)
grite issue dep add <A> --target <B> --type blocks --json

# Mark tasks as related (no ordering constraint)
grite issue dep add <A> --target <B> --type related_to --json

# List what an issue depends on
grite issue dep list <ID> --json

# List what depends on an issue (reverse)
grite issue dep list <ID> --reverse --json

# Get execution order (topological sort of open tasks)
grite issue dep topo --state open --json

Always run dep topo at session start to determine which task to work on next.

Context store

Index and query codebase structure for fast navigation:

# Index all tracked files (skips unchanged files)
grite context index --json

# Index specific files or patterns
grite context index --path src/main.py --json
grite context index --pattern "*.rs" --json

# Query for a symbol (function, class, struct, etc.)
grite context query <symbol_name> --json

# Show all symbols in a file
grite context show <file_path> --json

# Set project-level context (conventions, architecture notes)
grite context set <key> <value> --json

# View all project context
grite context project --json

Index after significant code changes to keep the symbol database current.

Key flags

  • --json - Use for all commands (machine-readable output)
  • --quiet - Suppress human output