.oorty Directory

Single source of truth for auto-generated files, caches, and analysis artifacts.

Overview

The .oorty/ directory centralizes all auto-generated infrastructure in one place. This makes cleanup simple, collaboration straightforward, and gitignoring predictable.

Directory Structure

.oorty/

.oorty/
├── cache/           # Ephemeral (gitignored)
│   └── plan-cache.json    # AI plan cache by file hash
├── plans/           # Shareable (tracked in git)
│   ├── test-plan.md       # Human-readable test plan
│   └── test-plan.json     # Machine-readable plan for generate
├── analysis/        # Ephemeral (gitignored)
│   └── coverage-report.json  # Coverage snapshots
└── logs/            # Ephemeral (gitignored)
    └── last-run.log       # Debug and audit logs

Subdirectories

cache/

gitignored

Ephemeral caching for performance optimization. Rebuilt locally on each machine.

plan-cache.json - Caches AI-generated test specs by file content hash
Prevents redundant AI calls when files haven't changed
Clear with npx oorty clean --cache

plans/

tracked in git

Test plans generated by oorty plan. Tracked in git for CI/CD and team collaboration.

test-plan.md - Human-readable test recommendations
test-plan.json - Machine-readable plan for oorty generate
Review and edit before generation
Commit to share test strategy with your team

analysis/

gitignored

Codebase analysis artifacts and coverage snapshots. Regenerated as needed.

coverage-report.json - Latest coverage data
testid-requirements.json - Missing data-testid analysis
Clear with npx oorty clean --analysis

logs/

gitignored

Debug and audit logs for troubleshooting CLI operations.

last-run.log - Most recent CLI execution log
Useful for debugging failed generations
Clear with npx oorty clean --logs

Git Strategy

The .oorty/ directory uses a hybrid gitignore strategy:

Directory	Git Status	Reason
.oorty/cache/	Ignored	Ephemeral, machine-specific
.oorty/plans/	Tracked	Valuable for CI and team collaboration
.oorty/analysis/	Ignored	Regenerated locally
.oorty/logs/	Ignored	Debug artifacts, machine-specific

.gitignore

# .gitignore
.oorty/cache/
.oorty/analysis/
.oorty/logs/
# Plans are tracked for CI/collaboration
# !.oorty/plans/ (implicit - not ignored)

Cleaning Up

Use the oorty clean command to manage the .oorty directory:

Terminal

# Clear all ephemeral data (cache, analysis, logs)
npx oorty clean
# Clear only cache
npx oorty clean --cache
# Clear only analysis
npx oorty clean --analysis
# Clear only logs
npx oorty clean --logs
# Clear plans (requires confirmation)
npx oorty clean --plans
# Clear everything including plans
npx oorty clean --all
# Skip confirmation prompts
npx oorty clean --yes

Migration from tests/plans/

If you have existing plans in tests/plans/, move them to .oorty/plans/ and update your oorty.json to set directories.plans to .oorty/plans.

Benefits

Single cleanup target - rm -rf .oorty/cache clears all caches
Portable collaboration - Team members get plans but rebuild caches locally
CI-friendly - Plans can be committed and used in CI pipelines
Predictable gitignore - Clear separation between ephemeral and tracked files
Easy debugging - Logs are centralized in one place

Next: oorty clean

Learn how to manage the .oorty directory with the clean command.

clean command