Skip to content

v

Jump to bottom
hbt edited this page Jul 3, 2025 · 1 revision

Verify and Test Changes

Comprehensive verification command that tests recent changes and validates implementations. This command automatically adds verification steps to plans and provides systematic testing of modifications.

Usage

  • /project:v - Auto-verify recent changes and implementations
  • /project:v functions - Test shell functions (like clr, setupClaudeServers)
  • /project:v configs - Verify configuration files and settings
  • /project:v commands - Test Claude Code custom commands
  • /project:v build - Run build, lint, and test commands
  • /project:v $ARGUMENTS - Custom verification focus

Verification Process

1. Analyze Recent Changes

  • Identify what was modified in the current session
  • Determine appropriate verification methods
  • Check for any new functions, configs, or commands

2. Execute Verification Steps

Based on the type of changes detected:

Shell Functions:

  • Source the updated files
  • Test function execution
  • Verify expected outputs
  • Check error handling

Configuration Files:

  • Validate syntax and structure
  • Test configuration loading
  • Verify environment variables
  • Check file permissions

Custom Commands:

  • Test command availability
  • Verify argument handling
  • Check output format
  • Validate help text

Code Changes:

  • Run linting tools
  • Execute test suites
  • Check build processes
  • Verify functionality

3. Report Results

  • Provide clear success/failure status
  • Show specific test outputs
  • Highlight any issues found
  • Suggest fixes for failures

Plan Integration

When in plan mode, automatically add verification steps after each major task:

1. **Task:** Implement feature X
   **Verify:** Run `/project:v functions` to test new functionality

2. **Task:** Update configuration
   **Verify:** Run `/project:v configs` to validate settings

3. **Task:** Add custom command
   **Verify:** Run `/project:v commands` to test new command

Smart Detection

The command intelligently detects what needs verification by:

  • Analyzing recent file modifications
  • Checking git status for changes
  • Identifying new functions or aliases
  • Detecting configuration updates
  • Recognizing command additions

Error Handling

  • Graceful handling of missing files
  • Clear error messages for failures
  • Rollback suggestions for critical issues
  • Alternative approaches when primary verification fails

Examples

After adding a shell function:

# /project:v functions
✅ Sourcing updated ai.bash
✅ Testing clr function availability
✅ Executing clr with test parameters
✅ Verifying error handling
✅ All functions verified successfully

After modifying configs:

# /project:v configs
✅ Validating CLAUDE.md syntax
✅ Checking .bashrc sourcing
✅ Testing environment variables
✅ Verifying file permissions
✅ All configurations verified successfully

General verification:

# /project:v
🔍 Analyzing recent changes...
✅ Shell functions: 1 function tested
✅ Configurations: 2 files validated
✅ Commands: 1 new command verified
✅ Build: All checks passed
✅ Verification complete - All systems operational

Integration with Existing Workflow

  • Works with TodoWrite for task verification
  • Integrates with git workflow for change detection
  • Compatible with existing custom commands
  • Follows project documentation patterns
  • Supports existing shell function testing patterns

Notes

  • Verification steps are non-destructive
  • Tests run in safe environments when possible
  • Provides both automated and manual verification options
  • Maintains detailed logs for troubleshooting
  • Supports rollback when issues are detected

Clone this wiki locally