ctx-cc 1.0.0 → 2.0.0

package/commands/status.md

@@ -1,95 +0,0 @@
----
-name: ctx:status
-description: Full status report
----
-
-<objective>
-Display comprehensive project status including phase, progress, context usage, and todos.
-</objective>
-
-<process>
-
-<step name="gather_status">
-Collect status from all CTX components:
-
-1. **Project** - Name, tech stack
-2. **Phase** - Current phase, progress
-3. **Context** - Usage percentage
-4. **Memory** - Fact counts
-5. **Todos** - Pending count
-6. **Integrations** - ArguSeek, ChunkHound status
-</step>
-
-<step name="display">
-```
-## CTX Status
-
-### Project
-**Name:** {project name}
-**Tech:** {language} + {framework}
-**Initialized:** {date}
-
-### Current Phase
-**Phase:** {phase name} ({phase number}/{total})
-**Goal:** {goal}
-**Progress:** {percentage}% ({completed}/{total} tasks)
-**Status:** {pending/in_progress/complete}
-
-### Context Budget
-**Current:** {percentage}%
-**Quality:** {Peak/Good/Degrading/Poor}
-**Recommendation:** {Continue/Consider checkpoint/Checkpoint now}
-
-```
-{context bar visualization}
-[████████████░░░░░░░░] 45%
-```
-
-### Memory
-| Tier | Facts |
-|------|-------|
-| Working | {count} |
-| Episodic | {count} |
-| Semantic | {count} |
-
-### Todos
-**Pending:** {count}
-**In Progress:** {count}
-**Completed:** {count}
-
-### Integrations
-| Tool | Status |
-|------|--------|
-| ArguSeek | {available/unavailable} |
-| ChunkHound | {indexed/not indexed/unavailable} |
-
-### Last Checkpoint
-**ID:** {id or "None"}
-**Created:** {timestamp or "N/A"}
-
----
-
-**Quick Actions:**
-- Continue work: `/ctx:do`
-- Verify phase: `/ctx:verify`
-- Save state: `/ctx:pause`
-- View phases: `/ctx:phase list`
-```
-</step>
-
-</process>
-
-<context_quality>
-| Usage | Quality | Action |
-|-------|---------|--------|
-| 0-30% | Peak | Continue |
-| 30-50% | Good | Continue |
-| 50-70% | Degrading | Consider checkpoint |
-| 70%+ | Poor | Checkpoint now |
-</context_quality>
-
-<success_criteria>
-- [ ] All status components displayed
-- [ ] Context budget clearly shown
-- [ ] Next actions suggested
-</success_criteria>

package/commands/update.md

@@ -1,117 +0,0 @@
----
-name: ctx:update
-description: Check for CTX updates and install if available
----
-
-<objective>
-Check for CTX updates, show what's new, and install if user confirms.
-</objective>
-
-<process>
-
-<step name="get_installed_version">
-Read installed version:
-
-```bash
-cat ~/.claude/ctx/VERSION 2>/dev/null
-```
-
-If VERSION file missing, treat as version 0.0.0.
-</step>
-
-<step name="check_latest_version">
-Check npm for latest version:
-
-```bash
-npm view ctx-cc version 2>/dev/null
-```
-
-If npm check fails:
-```
-Couldn't check for updates (offline or npm unavailable).
-
-To update manually: `npx ctx-cc --force`
-```
-</step>
-
-<step name="compare_versions">
-Compare installed vs latest:
-
-**If installed == latest:**
-```
-## CTX Update
-
-**Installed:** {version}
-**Latest:** {version}
-
-You're already on the latest version.
-```
-
-**If installed < latest:**
-Continue to show changes and confirm.
-</step>
-
-<step name="show_changes">
-Fetch changelog and show what's new:
-
-```
-## CTX Update Available
-
-**Installed:** {old version}
-**Latest:** {new version}
-
-### What's New
-────────────────────────────────────────────────────────────
-
-{changelog entries between versions}
-
-────────────────────────────────────────────────────────────
-
-**Note:** The installer will replace:
-- `~/.claude/commands/ctx/`
-- `~/.claude/ctx/`
-- `~/.claude/agents/ctx-*`
-
-Your custom files are preserved.
-```
-</step>
-
-<step name="confirm_update">
-Ask user to confirm:
-
-**Options:**
-- "Yes, update now"
-- "No, cancel"
-</step>
-
-<step name="run_update">
-If confirmed:
-
-```bash
-npx ctx-cc --force
-```
-
-Clear any update cache.
-</step>
-
-<step name="complete">
-```
-╔═══════════════════════════════════════════════════════════╗
-║  CTX Updated: v{old} → v{new}                             ║
-╚═══════════════════════════════════════════════════════════╝
-
-⚠️  Restart Claude Code to pick up the new commands.
-
-View full changelog: https://github.com/jufjuf/CTX/blob/main/CHANGELOG.md
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Installed version detected
-- [ ] Latest version checked
-- [ ] Changelog shown for new versions
-- [ ] User confirmation obtained
-- [ ] Update executed successfully
-</success_criteria>

package/commands/verify.md

@@ -1,151 +0,0 @@
----
-name: ctx:verify
-description: Three-level verification of current phase
----
-
-<objective>
-Verify the current phase implementation using three-level verification plus anti-pattern scanning.
-</objective>
-
-<process>
-
-<step name="load_phase">
-Load current phase from `.ctx/ROADMAP.md`.
-Load verification criteria from `.ctx/phases/{phase-id}/PLAN.md`.
-
-If no phase:
-```
-No phase to verify. Run `/ctx:plan <goal>` first.
-```
-</step>
-
-<step name="three_level_verification">
-For each artifact in the phase:
-
-### Level 1: EXISTS
-```
-Question: Is the file on disk?
-Check: Glob for the file path
-Pass: File exists
-Fail: File missing
-```
-
-### Level 2: SUBSTANTIVE
-```
-Question: Is it real code, not a stub?
-Check:
-  - No "// TODO" comments in new code
-  - No empty function bodies
-  - No placeholder returns (return null, return {})
-  - No "not implemented" comments
-Pass: Real, complete implementation
-Fail: Stub or placeholder detected
-```
-
-### Level 3: WIRED
-```
-Question: Is it imported and used?
-Check:
-  - Grep for imports of the file
-  - Trace call paths from entry points
-  - Verify the code is reachable
-Pass: Connected to the application
-Fail: Orphan code (exists but unused)
-```
-</step>
-
-<step name="anti_pattern_scan">
-Scan for common anti-patterns:
-
-| Pattern | Search | Severity |
-|---------|--------|----------|
-| TODO comments | `// TODO`, `# TODO` | Warning |
-| Empty catch | `catch.*\{\s*\}` | Error |
-| Console-only errors | `console.error` without throw | Warning |
-| Placeholder returns | `return null`, `return {}` | Error |
-| Hardcoded secrets | API keys, passwords | Critical |
-| Debug code | `console.log`, `debugger` | Warning |
-</step>
-
-<step name="goal_gap_analysis">
-Check if phase goal is achieved:
-
-1. Re-read the original goal
-2. Compare against what was built
-3. Identify any gaps
-
-```
-Goal: {original goal}
-Built: {what was implemented}
-Gaps: {missing pieces, if any}
-```
-</step>
-
-<step name="generate_report">
-Write `.ctx/phases/{phase-id}/VERIFY.md`:
-
-```markdown
-# Verification Report
-
-## Phase: {name}
-## Date: {timestamp}
-
-## Three-Level Results
-
-| Artifact | Exists | Substantive | Wired | Status |
-|----------|--------|-------------|-------|--------|
-| {file1}  | ✓      | ✓           | ✓     | PASS   |
-| {file2}  | ✓      | ✓           | ✗     | FAIL   |
-
-## Anti-Pattern Scan
-
-| Pattern | Count | Files | Severity |
-|---------|-------|-------|----------|
-| TODO    | 2     | auth.ts, login.ts | Warning |
-
-## Goal Gap Analysis
-
-**Goal:** {goal}
-**Status:** {Achieved / Partially Achieved / Not Achieved}
-**Gaps:** {list or "None"}
-
-## Overall: {PASS / FAIL}
-
-{If FAIL: List what needs to be fixed}
-```
-</step>
-
-<step name="output_summary">
-Display verification summary:
-
-```
-## Verification: {phase name}
-
-**Three-Level Check:**
-  - Exists: {pass/fail count}
-  - Substantive: {pass/fail count}
-  - Wired: {pass/fail count}
-
-**Anti-Patterns:** {count} found
-**Goal Gaps:** {count or "None"}
-
-**Overall:** {PASS ✓ / FAIL ✗}
-
-{If FAIL:}
-**Action Required:**
-  - {list of fixes needed}
-
-{If PASS:}
-**Next:** Run `/ctx:phase next` or `/ctx:ship`
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] All artifacts checked at three levels
-- [ ] Anti-pattern scan completed
-- [ ] Goal gap analysis done
-- [ ] VERIFY.md written
-- [ ] Clear pass/fail determination
-</success_criteria>