ragtime-cli 0.2.17__py3-none-any.whl → 0.3.0__py3-none-any.whl

src/commands/recall.md

@@ -1,175 +0,0 @@
----
-description: Search the local memory system for knowledge
-allowed-arguments: search query and optional filters (e.g., /recall auth patterns, /recall --namespace app)
-allowed-tools: mcp__ragtime__search, mcp__ragtime__list_memories, AskUserQuestion
----
-
-# Recall
-
-Search the local memory system for stored knowledge.
-
-**Usage:**
-- `/recall auth patterns` - Search for auth-related patterns
-- `/recall #301 decisions` - Decisions related to issue #301
-- `/recall --namespace team` - All team conventions
-- `/recall` - Interactive search mode
-
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     CUSTOMIZABLE: Modify query parsing, add project-specific filters,
-     adjust result formatting, etc.
-     ═══════════════════════════════════════════════════════════════════════════ -->
-
-## Query Syntax
-
-```
-/recall [modifiers] <search terms> [filters]
-```
-
-**Modifiers:**
-- `all:` - Include all confidence levels (default: high + medium only)
-- `pre-merge:` - Include unmerged branch memories from teammates
-
-**Filters:**
-- `#301` or `--issue 301` - Filter by issue number
-- `@auth` or `--component auth` - Filter by component
-- `--type decision` - Filter by memory type
-- `--namespace app` - Filter by namespace
-- `--status active` - Filter by status
-
-<!-- CUSTOMIZABLE: Add your own filter shortcuts -->
-
-## Step 1: Parse the Query
-
-**If `$ARGUMENTS` provided:**
-- Parse modifiers, search terms, and filters
-
-**If no arguments:**
-- Ask: "What are you looking for?"
-- Optionally ask for filters
-
-## Step 2: Build the Search
-
-Construct filters based on parsed query:
-
-- Default: exclude `status: "abandoned"` and `confidence: "low"`
-- If `all:` modifier: include everything
-- If `pre-merge:` modifier: include `status: "pre-merge"`
-
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     RAGTIME CORE - DO NOT MODIFY
-     These commands must match ragtime's expected format.
-     ═══════════════════════════════════════════════════════════════════════════ -->
-
-Execute the search:
-
-```
-mcp__ragtime__search:
-  query: "{search terms}"
-  namespace: "{namespace if specified}"
-  type: "{type if specified}"
-  component: "{component if specified}"
-  limit: 20
-```
-
-For listing without semantic search:
-
-```
-mcp__ragtime__list_memories:
-  namespace: "{namespace}"
-  type: "{type}"
-  status: "{status}"
-  component: "{component}"
-  limit: 20
-```
-
-<!-- ═══════════════════════════════════════════════════════════════════════════ -->
-
-## Step 3: Present Results
-
-Format results clearly:
-
-```
-## 🧠 Recall: "{search terms}"
-
-Found {count} memories:
-
-### High Confidence
-───────────────────────────────────────────
-
-**Auth uses JWT with 15-min expiry**
-- Type: architecture | Component: auth
-- Added: 2026-01-15 | Source: pr-graduate
-
-**Sessions stored in Redis, not cookies**
-- Type: decision | Component: auth
-- Added: 2026-01-10 | Source: meeting
-
-### Medium Confidence
-───────────────────────────────────────────
-
-**Consider rate limiting on auth endpoints**
-- Type: pattern | Component: auth
-- Added: 2026-01-20 | Source: remember
-
-───────────────────────────────────────────
-
-Showing {count} of {total} results.
-Refine with: /recall auth --type decision
-Include low confidence: /recall all: auth
-```
-
-### Pre-Merge Results
-
-If pre-merge memories are found, show them separately with a warning:
-
-```
-### ⚠️ Pre-Merge (from teammate branches)
-───────────────────────────────────────────
-
-**New auth middleware pattern** (pre-merge)
-- From: origin/jm/feature-auth
-- Type: architecture | Component: auth
-- ⚠️ Not yet merged - may change
-
-```
-
-## Step 4: Offer Actions
-
-```
-What would you like to do?
-
-1. **Use this context** - I'll incorporate these into our work
-2. **Refine search** - Try different filters
-3. **View details** - See full content of a specific memory
-4. **Done** - Just wanted to see what we know
-```
-
-## Example Queries
-
-| Query | What it finds |
-|-------|---------------|
-| `/recall auth` | All auth-related memories (high/medium confidence) |
-| `/recall #301 decisions` | Decisions made during issue #301 |
-| `/recall --namespace team` | All team conventions |
-| `/recall --component shifts --type architecture` | Shifts architecture |
-| `/recall pre-merge: auth` | Include teammate WIP auth knowledge |
-| `/recall all: validation` | Include low-confidence validation memories |
-
-## No Results Handling
-
-```
-No memories found for "{query}" with current filters.
-
-Suggestions:
-- Try broader terms: /recall {simpler query}
-- Include all confidence: /recall all: {query}
-- Check different namespace: /recall --namespace team {query}
-- Include pre-merge: /recall pre-merge: {query}
-```
-
-## Notes
-
-- Results are sorted by relevance (semantic similarity)
-- Default excludes low confidence and abandoned memories
-- Use `all:` modifier to see everything
-- Pre-merge memories are from `(unmerged)` folders synced from teammate branches

src/commands/remember.md

@@ -1,168 +0,0 @@
----
-description: Capture ad-hoc knowledge to local memory mid-session
-allowed-arguments: the thing to remember (e.g., /remember auth uses 15-min JWT expiry)
-allowed-tools: Bash, AskUserQuestion, mcp__ragtime__remember
----
-
-# Remember
-
-Capture ad-hoc knowledge to the local memory system during a session.
-
-**Usage:**
-- `/remember auth uses 15-minute JWT expiry` - Quick capture with content
-- `/remember` - Interactive mode, asks what to remember
-
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     CUSTOMIZABLE: Modify prompts, add project-specific types, adjust the
-     approval flow, etc. Everything above the RAGTIME CORE section can be
-     tailored to your project's needs.
-     ═══════════════════════════════════════════════════════════════════════════ -->
-
-## When to Use
-
-Use `/remember` when you discover something worth preserving:
-- Architecture patterns ("the validation pipeline works like X")
-- Gotchas ("don't use Y because Z")
-- Decisions made during discussion
-- Team preferences discovered
-- Anything you'd want future sessions to know
-
-**Don't use for:**
-- Temporary debug notes (those belong in handoff.md)
-- Personal todos (use GitHub issues)
-- Things that will be captured by `/pr-graduate` anyway
-
-## Step 1: Capture the Knowledge
-
-**If `$ARGUMENTS` provided:**
-- Use it as the memory content
-
-**If no arguments:**
-- Ask: "What would you like me to remember?"
-
-## Step 2: Determine Memory Type
-
-Ask the user:
-
-```
-What type of knowledge is this?
-
-1. 🏗️ **Architecture** - How something works in the codebase
-2. 📋 **Convention** - Team rule or standard practice
-3. ⚠️ **Gotcha** - Warning or "don't do this"
-4. 🎯 **Decision** - Why we chose X over Y
-5. 💡 **Pattern** - Reusable approach for common problem
-```
-
-<!-- CUSTOMIZABLE: Add your own types here if needed -->
-
-## Step 3: Determine Scope
-
-```
-Where does this knowledge apply?
-
-1. 🌐 **Global** - Applies everywhere
-2. 📦 **Component** - Specific area (auth, claims, shifts, etc.)
-3. 📄 **File** - Specific file or folder
-```
-
-If Component or File, ask which one.
-
-<!-- CUSTOMIZABLE: Add your own components here -->
-
-## Step 4: Determine Confidence
-
-```
-How confident are you in this knowledge?
-
-1. ✅ **High** - Verified, tested, or from authoritative source
-2. ⚡ **Medium** - Observed it working, but not extensively tested
-3. 🤔 **Low** - Best guess or inference, should be validated
-```
-
-## Step 5: Determine Namespace
-
-Based on the memory type, suggest the appropriate namespace:
-
-| Type | Default Namespace |
-|------|------------------|
-| Architecture | `app` |
-| Convention | `team` |
-| Gotcha | `app` |
-| Decision | `app` (or `branch-{branch}` if WIP) |
-| Pattern | `app` |
-
-Ask: "Store in `{suggested namespace}`? Or somewhere else?"
-
-<!-- CUSTOMIZABLE: Adjust routing rules for your project -->
-
-## Step 6: Confirm and Store
-
-Present the memory for confirmation:
-
-```
-## Memory to Store
-
-**Content:** {the knowledge}
-**Type:** {type}
-**Namespace:** {namespace}
-**Confidence:** {confidence}
-**Scope:** {scope}
-**Component:** {if applicable}
-
-Store this? (yes/edit/cancel)
-```
-
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     RAGTIME CORE - DO NOT MODIFY
-     These commands must match ragtime's expected format.
-     Changing these may break storage/retrieval.
-     ═══════════════════════════════════════════════════════════════════════════ -->
-
-Once confirmed, store using ragtime MCP:
-
-```
-mcp__ragtime__remember:
-  content: "{the knowledge}"
-  namespace: "{namespace}"
-  type: "{architecture|convention|decision|pattern}"
-  component: "{component if applicable}"
-  confidence: "{high|medium|low}"
-  confidence_reason: "manual"
-  source: "remember"
-```
-
-<!-- ═══════════════════════════════════════════════════════════════════════════ -->
-
-## Step 7: Confirm Storage
-
-```
-✅ Remembered!
-
-"{abbreviated content}..."
-
-Stored to: {namespace}
-Confidence: {confidence}
-Query with: ragtime search "{topic}" --namespace {namespace}
-```
-
-## Quick Mode
-
-For rapid capture, you can specify everything inline:
-
-```
-/remember [high] auth uses 15-min JWT expiry #auth #architecture
-```
-
-Parsing:
-- `[high]` → confidence
-- `#auth` → component
-- `#architecture` → type
-- Rest → content
-
-## Notes
-
-- Memories stored via `/remember` get `source: "remember"` and default to medium confidence unless specified
-- If on a feature branch, consider whether this is branch-specific or general knowledge
-- For decisions that might be reversed, use low confidence
-- Team conventions should be discussed before storing to `team` namespace

src/commands/save.md

@@ -1,10 +0,0 @@
----
-description: Save current progress (alias for /handoff)
-allowed-tools: Bash, Read, Write, mcp__ragtime__remember
----
-
-# Save
-
-Alias for `/handoff`. See that command for full documentation.
-
-Run `/handoff` to save current context to branch memory.

src/commands/start.md

@@ -1,206 +0,0 @@
----
-description: Start or resume work on a GitHub issue
-allowed-arguments: issue number (e.g., /start 230)
-allowed-tools: Bash, Read, Write, mcp__ragtime__search, mcp__ragtime__remember, AskUserQuestion
----
-
-# Start or Resume Work
-
-Smart command that starts fresh OR resumes existing work depending on context.
-
-**Usage:**
-- `/start 230` - Start or resume work on issue #230
-- `/start` - Show your assigned issues and prompt for selection
-
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     CUSTOMIZABLE: Adjust branch naming conventions, issue lookup, workflow
-     steps, etc.
-     ═══════════════════════════════════════════════════════════════════════════ -->
-
-## Step 1: Determine the Issue
-
-**If an issue number was provided as an argument**, use it directly.
-
-**If no argument was provided**, check current state and prompt:
-
-```bash
-BRANCH=$(git branch --show-current)
-ISSUE_NUM=$(echo "$BRANCH" | grep -oE '[0-9]+' | head -1)
-DEVNAME=$(gh api user --jq '.login' 2>/dev/null || git config user.name | tr ' ' '-' | tr '[:upper:]' '[:lower:]')
-
-echo "Current branch: $BRANCH"
-echo "Developer: $DEVNAME"
-
-if [ -n "$ISSUE_NUM" ]; then
-  echo "Already on issue branch: #$ISSUE_NUM"
-else
-  echo ""
-  echo "=== Your Assigned Issues ==="
-  gh issue list --assignee @me --state open
-fi
-```
-
-If not on an issue branch and no argument provided, ask: **"Which issue would you like to start?"**
-
-## Step 2: Switch to the Branch
-
-```bash
-ISSUE_NUM={issue_number}
-
-# Check if branch exists
-EXISTING_BRANCH=$(git branch -a | grep -E "/$ISSUE_NUM-|/$ISSUE_NUM$" | head -1 | tr -d ' *')
-
-if [ -n "$EXISTING_BRANCH" ]; then
-  echo "Found existing branch: $EXISTING_BRANCH"
-  git checkout "$EXISTING_BRANCH"
-else
-  # Create new branch
-  ISSUE_TITLE=$(gh issue view $ISSUE_NUM --json title --jq '.title' | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | tr -cd 'a-z0-9-' | head -c 40)
-  NEW_BRANCH="$DEVNAME/$ISSUE_NUM-$ISSUE_TITLE"
-  echo "Creating new branch: $NEW_BRANCH"
-  git checkout -b "$NEW_BRANCH" main
-fi
-```
-
-<!-- CUSTOMIZABLE: Adjust branch naming convention for your project -->
-
-## Step 3: Check for Existing Context
-
-```bash
-BRANCH=$(git branch --show-current)
-BRANCH_SLUG=$(echo "$BRANCH" | tr '/' '-')
-CONTEXT_FILE=".claude/memory/branches/$BRANCH_SLUG/context.md"
-
-if [ -f "$CONTEXT_FILE" ]; then
-  echo "✓ Found branch context"
-  cat "$CONTEXT_FILE"
-else
-  echo "No existing context found"
-fi
-```
-
-### Decision Tree:
-
-**If context.md exists:**
-→ **RESUME MODE** - Go to Step 4a
-
-**If NO context.md:**
-→ **FRESH START MODE** - Go to Step 4b
-
-## Step 4a: Resume Mode
-
-Load and present the existing context:
-
-1. Read the branch's `context.md`
-2. Display the current state and what's left
-3. Ask: "Ready to continue? What would you like to work on first?"
-
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     RAGTIME CORE - DO NOT MODIFY
-     ═══════════════════════════════════════════════════════════════════════════ -->
-
-Also load any branch memories:
-
-```
-mcp__ragtime__search:
-  query: "decisions patterns architecture"
-  namespace: "branch-{branch}"
-  limit: 10
-```
-
-<!-- ═══════════════════════════════════════════════════════════════════════════ -->
-
-Present:
-
-```
-## Resuming Issue #{issue_num}
-
-### Current State:
-{from context.md}
-
-### What's Left:
-{from context.md}
-
-### Branch Memories:
-{list of decisions/patterns stored}
-
-Ready to continue? What would you like to work on first?
-```
-
-## Step 4b: Fresh Start Mode
-
-Create a new implementation plan:
-
-1. Fetch issue details:
-   ```bash
-   gh issue view "$ISSUE_NUM" --json title,body,labels,assignees
-   ```
-
-2. Parse the GitHub issue (title, body, labels)
-
-3. Identify which parts of the app this touches
-
-<!-- ═══════════════════════════════════════════════════════════════════════════
-     RAGTIME CORE - DO NOT MODIFY
-     ═══════════════════════════════════════════════════════════════════════════ -->
-
-4. Search for relevant context:
-
-   **App knowledge (architecture for those areas):**
-   ```
-   mcp__ragtime__search:
-     query: "{component or feature area}"
-     namespace: "app"
-     limit: 10
-   ```
-
-   **Team conventions:**
-   ```
-   mcp__ragtime__search:
-     query: "conventions standards"
-     namespace: "team"
-     limit: 10
-   ```
-
-<!-- ═══════════════════════════════════════════════════════════════════════════ -->
-
-5. Create an implementation plan based on:
-   - Issue requirements
-   - Codebase knowledge from memories
-   - Team conventions
-
-6. Present the plan and ask if the user wants to proceed or adjust
-
-## Step 5: Save Initial Context (Fresh Start only)
-
-**After user approves the plan**, save it to context.md:
-
-```bash
-BRANCH=$(git branch --show-current)
-BRANCH_SLUG=$(echo "$BRANCH" | tr '/' '-')
-mkdir -p ".claude/memory/branches/$BRANCH_SLUG"
-```
-
-Write the context.md with the plan (see `/handoff` for format).
-
-## Step 6: Ready to Work
-
-```
-Ready to work on Issue #{issue_num}!
-
-What would you like to tackle first?
-```
-
-## Syncing Teammate Context
-
-If you need context from a teammate's branch:
-
-```bash
-# Fetch their branch
-git fetch origin jm/feature-auth
-
-# Sync their memories
-ragtime sync origin/jm/feature-auth
-```
-
-This creates `branches/jm-feature-auth(unmerged)/` with their context and memories, searchable but gitignored.