Project Detection Commands

VritraAI provides intelligent project detection and analysis tools that help you understand your project structure, dependencies, health, and optimization opportunities. These commands automatically detect project types, analyze dependencies, assess project health, and provide AI-powered recommendations.

Project Type Detection

project_type [directory]

Enhanced project type detection with AI analysis. Automatically identifies the type of project based on file structure, key files, and technologies used.

Features:

  • Automatic project type detection (Python, Node.js, Java, Go, Rust, C/C++, C#/.NET, Docker, etc.)
  • Primary and secondary type identification
  • Confidence scoring (High/Medium/Low)
  • Technology and framework detection
  • Key project files identification
  • Language distribution analysis
  • Build tools and package managers detection
  • AI-powered deeper analysis (when AI is enabled)

Detected Project Types:

  • Python: Detects requirements.txt, setup.py, pyproject.toml, Pipfile, conda.yml
  • Node.js: Detects package.json, package-lock.json, yarn.lock, node_modules
  • Java: Detects pom.xml, build.gradle, gradlew, mvnw
  • C#/.NET: Detects .csproj, .sln, packages.config, project.json
  • Go: Detects go.mod, go.sum, Gopkg.toml, glide.yaml
  • Rust: Detects Cargo.toml, Cargo.lock
  • Docker: Detects Dockerfile
  • Git Repository: Detects .git directory
  • C/C++: Detects Makefile

Parameters:

  • directory - (Optional) Directory to analyze. Defaults to current directory (.)

Examples:

# Detect current directory project type
project_type

# Detect project type in specific directory
project_type src/
project_type /path/to/project

Output Information:

  • Primary project type
  • Secondary types (if applicable)
  • Confidence level
  • Total files and code files count
  • Key project files (up to 10)
  • Technologies detected
  • Frameworks and libraries
  • AI-powered architecture assessment (when AI enabled)

Note: When AI is enabled, the command automatically performs deeper analysis including architecture assessment, purpose detection, technology stack analysis, complexity level, quality indicators, development stage, and recommendations.

Dependency Checking

dependencies_check [directory]

Check dependencies for security issues and updates. Analyzes dependency management files and provides insights about outdated packages, security vulnerabilities, and dependency health.

Features:

  • Automatic detection of dependency files
  • Support for multiple package managers
  • Security vulnerability analysis
  • Outdated dependency detection
  • AI-powered dependency analysis (when AI enabled)

Supported Dependency Files:

  • Node.js: package.json, package-lock.json, yarn.lock
  • Python: requirements.txt, Pipfile, poetry.lock, pyproject.toml
  • Ruby: Gemfile, Gemfile.lock
  • PHP: composer.json, composer.lock
  • Go: go.mod, go.sum
  • Rust: Cargo.toml, Cargo.lock
  • Java: pom.xml, build.gradle

Parameters:

  • directory - (Optional) Directory to check. Defaults to current directory (.)

Examples:

# Check dependencies in current directory
dependencies_check

# Check dependencies in specific directory
dependencies_check src/
dependencies_check /path/to/project

Analysis Includes:

  • Dependency count and listing
  • Version information
  • Security vulnerability assessment
  • Outdated package detection
  • AI-powered recommendations for updates and security fixes

Project Health Analysis

project_health [directory]

Comprehensive project health analysis that evaluates multiple aspects of your project and provides a health score with detailed recommendations.

Health Categories:

  • ๐Ÿ“š Documentation: README files, docs directories, documentation completeness
  • ๐Ÿงช Testing: Test files, test directories, test coverage indicators
  • ๐Ÿ“‚ Structure: Project organization, .gitignore, LICENSE, CHANGELOG, CI/CD configs
  • ๐Ÿ“ฆ Dependencies: Dependency management files, dependency health
  • ๐Ÿ”’ Security: Security best practices, potential secrets exposure, security configurations
  • ๐Ÿ”ง Maintenance: Git repository status, project activity indicators

Scoring System:

Each category is scored from 0-100, and an overall health score is calculated as the average of all category scores.

Parameters:

  • directory - (Optional) Directory to analyze. Defaults to current directory (.)

Examples:

# Analyze current directory health
project_health

# Analyze specific directory
project_health src/
project_health /path/to/project

AI-Powered Analysis:

When AI is enabled, the command provides:

  • Priority issues that need immediate attention
  • Step-by-step action plan to improve project health
  • Quick wins for easy improvements
  • Specific documentation recommendations
  • Testing strategy recommendations
  • Security hardening suggestions
  • Long-term maintenance recommendations
  • Industry best practices for the project type

Missing Files Suggestions

missing_files [directory]

AI-powered analysis that suggests missing files that would improve your project quality, maintainability, and completeness.

Features:

  • Analyzes project structure and existing files
  • Suggests missing documentation files
  • Recommends testing files and configurations
  • Suggests configuration files
  • Recommends security-related files
  • Provides development helper suggestions
  • Includes deployment configuration recommendations
  • Prioritizes suggestions (High/Medium/Low)

File Categories Suggested:

  • ๐Ÿ“š Documentation: README, CHANGELOG, API docs, etc.
  • ๐Ÿงช Testing: Test files, test configuration
  • ๐Ÿ”ง Configuration: Build files, CI/CD, linting configs
  • ๐Ÿ”’ Security: Security policies, .gitignore, etc.
  • ๐Ÿƒ Development: Development helpers, scripts
  • ๐Ÿ“ฆ Deployment: Docker files, deployment configs
  • ๐Ÿ“„ Legal: License, contributing guidelines
  • ๐ŸŽฏ Quality: Code quality tools, formatting configs

Parameters:

  • directory - (Optional) Directory to analyze. Defaults to current directory (.)

Examples:

# Get suggestions for current directory
missing_files

# Get suggestions for specific directory
missing_files src/

Requirement: This command requires AI to be enabled. Configure your API key first.

Project Optimization

project_optimize [directory]

AI-powered comprehensive project optimization that analyzes your entire project and provides detailed recommendations for improving structure, performance, maintainability, and best practices.

Features:

  • Comprehensive project structure analysis
  • File size and distribution analysis
  • Large file identification
  • Project health integration
  • Dependency analysis
  • AI-powered optimization recommendations
  • Prioritized action items

Analysis Includes:

  • Project type and structure
  • Total files and code files count
  • Project size (MB)
  • Language distribution
  • File type distribution
  • Large files identification (>1MB)
  • Health scores across all categories
  • Dependency management status

Parameters:

  • directory - (Optional) Directory to optimize. Defaults to current directory (.)

Examples:

# Optimize current directory project
project_optimize

# Optimize specific directory
project_optimize src/

AI Recommendations Include:

  • Project structure improvements
  • File organization recommendations
  • Performance optimizations
  • Dependency management improvements
  • Documentation enhancements
  • Testing strategy improvements
  • Security hardening suggestions
  • Build and deployment optimizations

Requirement: This command requires AI to be enabled. Configure your API key first.

Project Command

project [analyze]

General project command that shows basic project information or performs deep AI-powered project analysis.

Usage:

  • project - Show current project type and working directory
  • project analyze - Perform deep AI-powered project structure analysis

Examples:

# Show basic project info
project

# Deep AI analysis
project analyze

Note: The project analyze subcommand requires AI to be enabled.

Best Practices

  • Start with project_type: Understand your project structure before running other analyses
  • Check dependencies regularly: Use dependencies_check to keep dependencies secure and up-to-date
  • Monitor project health: Run project_health periodically to track project quality
  • Use missing_files: Get suggestions for improving project completeness
  • Optimize iteratively: Use project_optimize to get comprehensive improvement recommendations
  • Combine commands: Use multiple commands together for comprehensive project understanding

๐Ÿ’ก Pro Tip: Run project_type first to understand your project, then use project_health to assess quality, followed by project_optimize for comprehensive improvement recommendations.