/is - State Verification

Verify current state of systems, services, installations, and configurations.

System Prompt

⚠️ EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

1. IMMEDIATELY execute - no questions, no explanations first
2. Parse the query to identify what state to check
3. Run verification commands to check actual state
4. Report definitively with YES/NO and evidence

DO NOT:

• Assume state without checking
• Give uncertain answers when verification is possible

The user invoking the command IS the confirmation.

---

Usage

/is <state-query>

Query Patterns

Query Pattern	Purpose	Verification Method
/is X installed	Installation check	which, command -v, package managers
/is X running	Process check	pgrep, ps, systemctl status
/is X configured	Config check	File existence, env vars
/is X enabled	Feature check	Config files, flags
/is X up to date	Version check	Compare installed vs latest
/is the build passing	CI check	GitHub Actions, git status

Execution Steps

Step 1: Parse State Query

# Identify subject and state type
# Common states: installed, running, configured, enabled, passing, valid

Step 2: Run Verification

# For installation
which "$SUBJECT" 2>/dev/null || command -v "$SUBJECT" 2>/dev/null
# Check package managers
brew list "$SUBJECT" 2>/dev/null
pip show "$SUBJECT" 2>/dev/null
npm list "$SUBJECT" 2>/dev/null

# For running processes
pgrep -x "$SUBJECT" || ps aux | grep -v grep | grep "$SUBJECT"
# For services
systemctl is-active "$SUBJECT" 2>/dev/null || \
launchctl list | grep "$SUBJECT"

# For configuration
[ -f "$CONFIG_PATH" ] && echo "configured"
[ -n "$ENV_VAR" ] && echo "set"

# For CI status
gh run list --limit 1 --json status,conclusion

Step 3: Report Result

# Format: YES/NO + evidence + how to fix (if NO)

Response Format

┌─────────────────────────────────────────────────────────────────┐
│  /is: <query>                                                   │
├─────────────────────────────────────────────────────────────────┤
│  STATE VERIFICATION                                             │
│  ──────────────────                                             │
│                                                                 │
│  ✅ YES / ❌ NO                                                  │
│                                                                 │
│  Subject: <subject>                                             │
│  State: <state being checked>                                   │
│                                                                 │
│  EVIDENCE                                                       │
│  ────────                                                       │
│  <command output or verification result>                        │
│                                                                 │
│  [If YES] Details:                                              │
│    Version: X.Y.Z                                               │
│    Location: /path/to/binary                                    │
│    Status: active/running/enabled                               │
│                                                                 │
│  [If NO] To Fix:                                                │
│    <command to install/enable/configure>                        │
│                                                                 │
├─────────────────────────────────────────────────────────────────┤
│  Verified: <timestamp>                                          │
└─────────────────────────────────────────────────────────────────┘

Examples

Installation Check

/is docker installed

Output:

✅ YES

Subject: docker
State: installed

EVIDENCE:
$ which docker
/usr/local/bin/docker

Details:
  Version: 24.0.7
  Location: /usr/local/bin/docker
  Docker Desktop: Running

Service Running Check

/is the context watcher running

Output:

✅ YES

Subject: coditect-context-watcher
State: running

EVIDENCE:
$ launchctl list | grep coditect
12345  0  ai.coditect.context-watcher

Details:
  PID: 12345
  Status: Running
  Config: ~/Library/LaunchAgents/ai.coditect.context-watcher.plist

Configuration Check

/is CODITECT configured

Output:

✅ YES

Subject: CODITECT
State: configured

EVIDENCE:
✓ ~/.coditect symlink exists → ~/Library/Application Support/CODITECT/core
✓ machine-id.json present
✓ .venv activated
✓ databases initialized

Details:
  Installation: Protected location
  Machine UUID: d3d3a316-09c6-8f41-4a3f-d93e422d199c

Build Status Check

/is the build passing

Output:

❌ NO

Subject: CI build
State: failing

EVIDENCE:
$ gh run list --limit 1
✗ Build  main  failure  2m ago

Details:
  Workflow: CI
  Status: failure
  Failed step: test-unit

To Fix:
  1. gh run view --log-failed
  2. Fix failing tests
  3. Push and retry

Up-to-Date Check

/is node up to date

Output:

⚠️ OUTDATED

Subject: node
State: outdated

EVIDENCE:
Installed: v20.10.0
Latest: v22.1.0

To Fix:
  nvm install 22
  # or
  brew upgrade node

Related Commands

Command	Purpose
/can <action>	Check capabilities
/does <action>	Verify behavior
/will <prediction>	Predict future state
/what <component>	Discover components
/where <component>	Find locations

Success Output

✅ COMMAND COMPLETE: /is
Query: <query>
State: YES/NO
Subject: <subject>
Verified: <timestamp>

Completion Checklist

Before marking complete:

• Subject identified
• State type determined
• Verification command run
• Result clearly stated
• Fix provided (if NO)

Failure Indicators

This command has FAILED if:

• ❌ No query provided
• ❌ State assumed without verification
• ❌ No evidence provided
• ❌ No fix offered when state is NO

When NOT to Use

Do NOT use when:

• Need capability check (use /can)
• Need behavior verification (use /does)
• Need future prediction (use /will)

Principles

This command embodies:

• #9 Based on Facts - Always verify, never assume
• #6 Clear, Understandable - Definitive YES/NO
• #3 Complete Execution - Include fix if needed

Full Standard: CODITECT-STANDARD-AUTOMATION.md

---

Version: 1.0.0 Created: 2026-02-04 Author: CODITECT Team Framework: 5W+H Question Framework