improve

Improve — Framework Self-Improvement

Analyze the current project state and improve the .codex/ configuration for better AI assistance.

Usage

/improve                  — Full improvement pass (all areas)
/improve agents-md        — Update AGENTS.md only (fill placeholders, add patterns)
/improve rules            — Update rule file patterns to match actual project
/improve settings         — Update permissions and model config
/improve agents           — Tune agent tools and models for project needs
/improve scan             — Report only, no changes (dry run)

Process

Phase 1: Project Discovery

Scan the project to build a comprehensive profile:

1. Tech stack detection:

# Package managers and dependency files
ls package.json requirements.txt Pipfile go.mod Cargo.toml build.gradle pom.xml Gemfile composer.json sfdx-project.json 2>/dev/null

1. File type census:

find . -type f -not -path "*/.git/*" -not -path "*/node_modules/*" -not -path "*/__pycache__/*" -not -path "*/vendor/*" -not -path "*/.next/*" -not -path "*/dist/*" -not -path "*/build/*" | sed 's/.*\.//' | sort | uniq -c | sort -rn | head -20

1. Framework detection: Read config files (next.config., vite.config., angular.json, etc.)

2. Directory structure: Map the top-level architecture

3. Existing tooling: Find linter configs, test configs, CI configs

Phase 2: AGENTS.md Improvement

Read current AGENTS.md and check:

1. Unfilled placeholders: Find any remaining {{...}} and fill from discovered data:
   • {{PROJECT_DESCRIPTION}} — from README.md, package.json description, etc.
   • {{TECH_STACK_TABLE}} — build from dependency files
   • {{CODE_STRUCTURE}} — generate directory tree
   • {{CODING_STANDARDS}} — infer from linter configs (.eslintrc, .prettierrc, pyproject.toml, etc.)
   • {{ERROR_HANDLING_PATTERN}} — find common error patterns in code
   • {{TESTING_STRATEGY}} — infer from test config and existing tests
   • {{INTEGRATIONS}} — list discovered external services