@ranger-testing/ranger-cli 1.0.14 → 1.1.0

package/build/commands/sessionStartHook.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"sessionStartHook.js","sourceRoot":"","sources":["../../src/commands/sessionStartHook.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,6BAA6B,EAAE,MAAM,yBAAyB,CAAC;AACxE,OAAO,EAAE,QAAQ,EAAE,MAAM,qBAAqB,CAAC;AAE/C;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,gBAAgB;IAClC,yCAAyC;IACzC,MAAM,KAAK,GAAG,MAAM,QAAQ,EAAE,CAAC;IAE/B,IAAI,CAAC,KAAK,EAAE,CAAC;QACT,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;QAC5B,OAAO,CAAC,GAAG,CAAC,uBAAuB,CAAC,CAAC;QACrC,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;QAC5B,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,mDAAmD,CAAC,CAAC;QACjE,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,6CAA6C,CAAC,CAAC;QAC3D,OAAO,CAAC,GAAG,CAAC,8CAA8C,CAAC,CAAC;QAC5D,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,yDAAyD,CAAC,CAAC;QACvE,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,+CAA+C,CAAC,CAAC;QAC7D,OAAO,CAAC,GAAG,CAAC,8BAA8B,CAAC,CAAC;QAC5C,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,gDAAgD,CAAC,CAAC;QAC9D,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;QAC5B,OAAO;IACX,CAAC;IAED,MAAM,YAAY,GAAG,6BAA6B,EAAE,CAAC;IAErD,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;IAC5B,OAAO,CAAC,GAAG,CAAC,8CAA8C,CAAC,CAAC;IAC5D,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;IAC5B,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CACP,+DAA+D,CAClE,CAAC;IACF,OAAO,CAAC,GAAG,CACP,iEAAiE,CACpE,CAAC;IACF,OAAO,CAAC,GAAG,CAAC,wDAAwD,CAAC,CAAC;IACtE,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CAAC,wBAAwB,CAAC,CAAC;IACtC,OAAO,CAAC,GAAG,CAAC,YAAY,CAAC,CAAC;IAC1B,OAAO,CAAC,GAAG,CAAC,sBAAsB,CAAC,CAAC;IACpC,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;IAC5B,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CAAC,wDAAwD,CAAC,CAAC;IACtE,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CACP,uFAAuF,CAC1F,CAAC;IACF,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CAAC,8BAA8B,CAAC,CAAC;IAC5C,OAAO,CAAC,GAAG,CACP,8EAA8E,CACjF,CAAC;IACF,OAAO,CAAC,GAAG,CACP,mFAAmF,CACtF,CAAC;IACF,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CAAC,kCAAkC,CAAC,CAAC;IAChD,OAAO,CAAC,GAAG,CACP,4EAA4E,CAC/E,CAAC;IACF,OAAO,CAAC,GAAG,CACP,qFAAqF,CACxF,CAAC;IACF,OAAO,CAAC,GAAG,CACP,iFAAiF,CACpF,CAAC;IACF,OAAO,CAAC,GAAG,EAAE,CAAC;IACd,OAAO,CAAC,GAAG,CAAC,iCAAiC,CAAC,CAAC;IAE/C,4DAA4D;IAC5D,gDAAgD;IAChD,yBAAyB;AAC7B,CAAC"}

package/build/commands/utils/mcpConfig.js

@@ -1 +0,0 @@
-(function(_0x27e776,_0xc57177){const _0x37632e=_0x4c02,_0x4fa91c=_0x27e776();while(!![]){try{const _0x698b7b=-parseInt(_0x37632e(0x200))/0x1*(parseInt(_0x37632e(0x207))/0x2)+parseInt(_0x37632e(0x208))/0x3+-parseInt(_0x37632e(0x1fc))/0x4*(-parseInt(_0x37632e(0x1fa))/0x5)+-parseInt(_0x37632e(0x1f9))/0x6+parseInt(_0x37632e(0x1f2))/0x7*(parseInt(_0x37632e(0x201))/0x8)+-parseInt(_0x37632e(0x1f8))/0x9*(-parseInt(_0x37632e(0x203))/0xa)+-parseInt(_0x37632e(0x1f6))/0xb;if(_0x698b7b===_0xc57177)break;else _0x4fa91c['push'](_0x4fa91c['shift']());}catch(_0x8d7fa5){_0x4fa91c['push'](_0x4fa91c['shift']());}}}(_0x283a,0x2654a));function _0x4c02(_0x4b42e5,_0x4572ed){_0x4b42e5=_0x4b42e5-0x1f1;const _0x283a73=_0x283a();let _0x4c02c4=_0x283a73[_0x4b42e5];return _0x4c02c4;}import{readFile,writeFile}from'fs/promises';import{existsSync}from'fs';import{join}from'path';export function getMcpConfigPath(){const _0x28f1eb=_0x4c02,_0x24abcf={'CGcdp':_0x28f1eb(0x1f1)};return join(process[_0x28f1eb(0x205)](),_0x24abcf[_0x28f1eb(0x1f3)]);}export async function loadMcpConfig(){const _0x98aee2=_0x4c02,_0x53c790={'ldcmE':function(_0x261f2d){return _0x261f2d();},'wtgsG':function(_0x1ed47d,_0x47df48,_0x586c84){return _0x1ed47d(_0x47df48,_0x586c84);},'gYpqY':_0x98aee2(0x204)},_0x46ff4a=_0x53c790[_0x98aee2(0x1fb)](getMcpConfigPath);if(existsSync(_0x46ff4a))try{const _0x29829d=await _0x53c790[_0x98aee2(0x1fd)](readFile,_0x46ff4a,_0x53c790['gYpqY']);return JSON['parse'](_0x29829d);}catch{return{'mcpServers':{}};}return{'mcpServers':{}};}export async function saveMcpConfig(_0x836328){const _0x4ada1f=_0x4c02,_0x2e223d={'XENCi':function(_0xbd4c68){return _0xbd4c68();},'UyrCZ':function(_0x15ec54,_0x532786,_0x156835){return _0x15ec54(_0x532786,_0x156835);}},_0x56a87e=_0x2e223d['XENCi'](getMcpConfigPath);await _0x2e223d[_0x4ada1f(0x202)](writeFile,_0x56a87e,JSON[_0x4ada1f(0x1f7)](_0x836328,null,0x2));}export function hasRangerServer(_0x15690f){const _0x269dde=_0x4c02;return!!_0x15690f[_0x269dde(0x206)]['ranger'];}function _0x283a(){const _0x44dc41=['mcpServers','5386fEHwAV','642120LpvByj','.mcp.json','7vnwIsI','CGcdp','@ranger-testing/ranger-cli','ranger','4018938pyiKSZ','stringify','489609HkUlHK','564618gkViqW','856210EAgSbt','ldcmE','4reGHCr','wtgsG','MzoMI','npx','101bRhJcl','1849352KNyfkJ','UyrCZ','50lwfBej','utf-8','cwd'];_0x283a=function(){return _0x44dc41;};return _0x283a();}export function setRangerServer(_0x15b49c){const _0x18ddc1=_0x4c02,_0x466c38={'nISnc':_0x18ddc1(0x1ff),'MzoMI':_0x18ddc1(0x1f4),'aUwTs':'data-mcp-server'};_0x15b49c['mcpServers'][_0x18ddc1(0x1f5)]={'command':_0x466c38['nISnc'],'args':[_0x466c38[_0x18ddc1(0x1fe)],_0x466c38['aUwTs']]};}

package/build/commands/utils/mcpConfig.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"mcpConfig.js","sourceRoot":"","sources":["../../../src/commands/utils/mcpConfig.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,SAAS,EAAE,MAAM,aAAa,CAAC;AAClD,OAAO,EAAE,UAAU,EAAE,MAAM,IAAI,CAAC;AAChC,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAC;AAY5B,MAAM,UAAU,gBAAgB;IAC5B,OAAO,IAAI,CAAC,OAAO,CAAC,GAAG,EAAE,EAAE,WAAW,CAAC,CAAC;AAC5C,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,aAAa;IAC/B,MAAM,aAAa,GAAG,gBAAgB,EAAE,CAAC;IACzC,IAAI,UAAU,CAAC,aAAa,CAAC,EAAE,CAAC;QAC5B,IAAI,CAAC;YACD,MAAM,cAAc,GAAG,MAAM,QAAQ,CAAC,aAAa,EAAE,OAAO,CAAC,CAAC;YAC9D,OAAO,IAAI,CAAC,KAAK,CAAC,cAAc,CAAC,CAAC;QACtC,CAAC;QAAC,MAAM,CAAC;YACL,8BAA8B;YAC9B,OAAO,EAAE,UAAU,EAAE,EAAE,EAAE,CAAC;QAC9B,CAAC;IACL,CAAC;IACD,OAAO,EAAE,UAAU,EAAE,EAAE,EAAE,CAAC;AAC9B,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,aAAa,CAAC,MAAiB;IACjD,MAAM,aAAa,GAAG,gBAAgB,EAAE,CAAC;IACzC,MAAM,SAAS,CAAC,aAAa,EAAE,IAAI,CAAC,SAAS,CAAC,MAAM,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,CAAC;AACpE,CAAC;AAED,MAAM,UAAU,eAAe,CAAC,MAAiB;IAC7C,OAAO,CAAC,CAAC,MAAM,CAAC,UAAU,CAAC,MAAM,CAAC;AACtC,CAAC;AAED,MAAM,UAAU,eAAe,CAAC,MAAiB;IAC7C,iEAAiE;IACjE,qCAAqC;IACrC,MAAM,CAAC,UAAU,CAAC,MAAM,GAAG;QACvB,OAAO,EAAE,KAAK;QACd,IAAI,EAAE,CAAC,4BAA4B,EAAE,iBAAiB,CAAC;KAC1D,CAAC;AACN,CAAC"}

package/build/skills/feature-tracker/SKILL.md

@@ -1,163 +0,0 @@
----
-name: feature-tracker
-description: "Ranger's core development workflow for building e2e features. Use this skill for ANY feature development, implementation, or code changes that touches UI. Automatically tracks progress with checklist items, verifies implementations in the browser, and generates completion reports with evidence. Start every coding task by checking for existing features to resume."
----
-
-You are a Feature Development Agent. Your job is to systematically implement features while tracking progress with verifiable checklist items. Every implementation gets verified in the browser with evidence (screenshots, traces, conversation logs).
-
-# When to Use This Skill
-
-Use this skill for ANY substantial feature work:
-- Building new features
-- Multi-step development tasks
-- Code changes that should be verified
-- Continuing previous feature work
-
-# Workflow Overview
-
-```
-┌───────────────────────────────────────┐
-│  1. RESUME OR CREATE FEATURE        │  ◀── Skill: start.md, create.md
-│     • Resume existing feature         │
-│     • OR create new feature           │
-└───────────────────┬───────────────────┘
-                    │
-                    ▼
-        ┌───────────────────────┐
-        │                       │
-        │   ┌───────────────┐   │
-        │   │ 2. IMPLEMENT  │   │  ◀── You write code (not covered by skill)
-        │   │    in code    │   │
-        │   └───────┬───────┘   │
-        │           │           │
-        │           ▼           │
-        │   ┌───────────────┐   │
-        │   │  3. VERIFY    │   │  ◀── Skill: verify.md
-        │   │  in browser   │   │
-        │   └───────┬───────┘   │
-        │           │           │
-        │           ▼           │
-        │     More items?       │
-        │       YES ─┘          │
-        │                       │
-        └───────────┬───────────┘
-                    │ NO (all verified)
-                    ▼
-┌───────────────────────────────────────┐
-│  4. REPORT                            │  ◀── Skill: report.md
-│     • Generate completion report      │
-│     • Share with user                 │
-└───────────────────────────────────────┘
-```
-
----
-
-# Step 1: Resume or Create Feature
-
-**Goal:** Have an active feature with a checklist before you start coding.
-
-### Resume Existing Feature
-
-Check if there's a feature to resume from the current git context:
-
-```bash
-ranger feature resume
-ranger feature show
-```
-
-See [start.md](./start.md) for details on resuming features.
-
-### Create New Feature
-
-If no existing feature, create one with a detailed checklist:
-
-```bash
-ranger feature create "Feature Name" \
-  --description "Comprehensive description of what this feature does" \
-  -c "Detailed item 1" \
-  -c "Detailed item 2" \
-  -c "Detailed item 3"
-```
-
-See [create.md](./create.md) for details on writing good descriptions.
-
----
-
-# Step 2: Implement in Code
-
-**Goal:** Write the code for a checklist item.
-
-This step is your normal coding work - not covered by this skill. Write the implementation for one or more checklist items.
-
----
-
-# Step 3: Verify in Browser
-
-**Goal:** Verify each implementation works and capture evidence.
-
-After implementing, verify in the browser:
-
-```bash
-ranger verify-feature --task "Detailed description of what to verify"
-```
-
-The URL is derived from your active environment's `baseUrl` setting. Use `--env` to specify a different environment.
-
-The verification agent will:
-1. Execute the task in a real browser
-2. Evaluate if the checklist item is satisfied
-3. Mark the item as verified, partial, blocked, or failed
-4. Link the session evidence (trace, screenshots)
-
-See [verify.md](./verify.md) for details on writing good verification tasks.
-
-### Repeat
-
-Continue the **Implement → Verify** cycle for each checklist item until all are verified.
-
----
-
-# Step 4: Report
-
-**Goal:** Generate a completion report with all evidence.
-
-When all items are verified (feature auto-completes), generate a report:
-
-```bash
-ranger feature report
-```
-
-Share the report with the user:
-
-> Feature complete! All checklist items verified.
-> **Report:** [.ranger/reports/feat_abc123.md](.ranger/reports/feat_abc123.md)
-
-See [report.md](./report.md) for report contents and sharing.
-
----
-
-# Quick Reference
-
-| Command | Purpose |
-|---------|---------|
-| `ranger feature resume` | Find & resume feature by git context |
-| `ranger feature show` | Show current feature status |
-| `ranger feature create` | Create new feature with checklist |
-| `ranger verify-feature` | Verify item in browser |
-| `ranger feature report` | Generate completion report |
-
-# Skill Files
-
-| File | Covers |
-|------|--------|
-| [start.md](./start.md) | Resuming features, listing features, git context |
-| [create.md](./create.md) | Creating features, writing good descriptions |
-| [verify.md](./verify.md) | Browser verification, evaluation results |
-| [report.md](./report.md) | Generating and sharing reports |
-
-# Key Principles
-
-1. **Always check for existing features first** - Run `ranger feature resume` at session start
-2. **Be very descriptive** - Detailed descriptions help verification agents evaluate results
-3. **Verify after implementing** - Don't skip browser verification
-4. **Generate reports** - Provide evidence of completion to users

package/build/skills/feature-tracker/create.md

@@ -1,114 +0,0 @@
-# Creating a New Feature
-
-Create a feature when starting new work that doesn't have an existing feature to resume.
-
-## Basic Command
-
-```bash
-ranger feature create "<feature name>" \
-  --description "<description>" \
-  -c "<checklist item 1>" \
-  -c "<checklist item 2>"
-```
-
-Use multiple `-c` flags for multiple checklist items. Each item can contain commas.
-
-## What Gets Captured Automatically
-
-When you create a feature, the CLI automatically captures:
-- **Git repo URL** - From `git remote get-url origin`
-- **Git branch** - From current branch name
-- **Created timestamp**
-- **Your organization** - From API token
-
-This enables `ranger feature resume` to find features by git context later.
-
-## Writing Good Checklist Items
-
-**OPTIMIZE FOR FAST FEEDBACK: Keep checklists as small as possible.**
-
-### Key Principles
-
-1. **Prefer 1 checklist item** when possible - this gets you feedback fastest
-2. **Each item should be a full user flow**, not a single UI element
-3. **Only add more items for larger features** that genuinely have multiple distinct flows
-
-### What Makes a Good Checklist Item
-
-Each checklist item should describe the **complete user journey** to verify the feature:
-
-**Bad - too granular:**
-```
-Button appears on page
-```
-
-**Good - full user flow:**
-```
-Navigate to Settings page, see the new Export button, click it, and verify the export dialog opens with CSV and PDF options
-```
-
-**Bad - broken into too many items:**
-```
-1. Login button exists
-2. Login form appears
-3. Login submits correctly
-4. Redirects to dashboard
-```
-
-**Good - single flow:**
-```
-Go to login page, enter valid credentials, submit, and verify redirect to dashboard with user info displayed
-```
-
-### When to Use Multiple Items
-
-Only split into multiple items when the feature has **genuinely distinct user flows**:
-
-- Adding a button? **1 item** - navigate, find it, use it, verify result
-- Building login + signup? **2 items** - each is a separate flow
-- Full CRUD feature? **3-4 items** - create, read, update, delete are distinct
-
-## Complete Example
-
-**Simple feature (1 item):**
-```bash
-ranger feature create "Add Export Button" \
-  --description "Add export functionality to the reports page" \
-  -c "Navigate to Reports page, click the new Export button, select CSV format, and verify the file downloads"
-```
-
-**Larger feature (multiple items):**
-```bash
-ranger feature create "User Authentication" \
-  --description "Login and signup flows for the web app" \
-  -c "Go to login page and sign in with valid credentials, verify redirect to dashboard" \
-  -c "Go to signup page and create new account, verify welcome email and successful login"
-```
-
-## Output
-
-```
-Creating feature...
-
-✅ Feature created: feat_01abc123
-
-🔄 User Authentication (feat_01abc123)
-   Status: in_progress
-   Description: Login and signup flows...
-   Repository: github.com/myorg/myapp
-   Branch: feature/auth
-   Created: 1/21/2026, 10:30:00 AM
-
-   Checklist:
-   1. ⬜ Go to login page and sign in...
-   2. ⬜ Go to signup page and create...
-
-➡️  Set as active feature
-```
-
-## After Creation
-
-The new feature is automatically set as the active feature. You can now:
-
-1. Start implementing the first checklist item
-2. View status with `ranger feature show`

package/build/skills/feature-tracker/report.md

@@ -1,159 +0,0 @@
-# Generating Reports
-
-When a feature is complete (or you need a status update), generate a report with all verification evidence.
-
-## Basic Command
-
-```bash
-ranger feature report
-```
-
-This creates a markdown file at `.ranger/reports/<feature-id>.md`
-
-## Options
-
-```bash
-# Report for active feature
-ranger feature report
-
-# Report for specific feature
-ranger feature report feat_abc123
-
-# Custom output path
-ranger feature report --output ./my-report.md
-```
-
-## When to Generate Reports
-
-1. **Feature complete** - All items verified, share with stakeholders
-2. **Progress update** - Show what's done and what's remaining
-3. **Blocked status** - Document what's blocking and what evidence exists
-4. **Handoff** - Another developer taking over the feature
-
-## Report Contents
-
-The generated report includes:
-
-### Header
-- Feature name and ID
-- Current status (in_progress, completed, blocked)
-- Git context (repo, branch)
-- Created/completed dates
-
-### Description
-- Full feature description
-
-### Checklist Progress
-- Each item with status emoji
-- Verification details (date, session ID)
-- Agent summary of what was verified
-- Links to Playwright traces
-- Blocked/canceled reasons
-
-### Blocking Issues
-- Summary of any blocked items
-- Reasons and context
-
-### Verification Sessions
-- Table of all browser sessions
-- Item, status, duration, date
-
-## Example Report
-
-```markdown
-# Feature Report: User Authentication
-
-**Status:** ✅ Completed
-**Created:** Jan 20, 2026
-**Completed:** Jan 21, 2026
-**Repository:** github.com/myorg/myapp
-**Branch:** feature/auth
-
-## Description
-
-Complete user authentication system including login, signup, and password reset.
-
-## Checklist Progress (3/3 verified)
-
-### ✅ User can log in with valid credentials
-
-- **Verified:** Jan 20, 2026
-- **Session:** bsess_abc123
-- **Summary:** Successfully logged in with test credentials, verified redirect to dashboard
-- **Trace:** [View in Playwright](https://trace.playwright.dev/?trace=...)
-
-### ✅ User can sign up with new account
-
-- **Verified:** Jan 21, 2026
-- **Session:** bsess_def456
-- **Summary:** Created new account, verified welcome email received
-- **Trace:** [View in Playwright](https://trace.playwright.dev/?trace=...)
-
-### ✅ User can reset password
-
-- **Verified:** Jan 21, 2026
-- **Session:** bsess_ghi789
-- **Summary:** Completed password reset flow, verified new password works
-- **Trace:** [View in Playwright](https://trace.playwright.dev/?trace=...)
-
-## Blocking Issues
-
-None
-
-## All Verification Sessions
-
-| Session | Item | Status | Duration | Date |
-|---------|------|--------|----------|------|
-| bsess_abc123 | Login | ✅ completed | 45s | Jan 20, 2026 |
-| bsess_def456 | Signup | ✅ completed | 62s | Jan 21, 2026 |
-| bsess_ghi789 | Reset | ✅ completed | 38s | Jan 21, 2026 |
-```
-
-## Sharing with Users
-
-After generating a report, share it with the user:
-
-```
-Feature complete! All 3 checklist items verified.
-
-**Report:** [.ranger/reports/feat_abc123.md](.ranger/reports/feat_abc123.md)
-
-Summary:
-- ✅ Login flow - working correctly
-- ✅ Signup flow - creates account and sends verification email
-- ✅ Password reset - full flow working
-
-Each item has a Playwright trace link for detailed session replay.
-```
-
-## Playwright Traces
-
-Each verification session records a Playwright trace. Click the trace link to:
-- See every browser action
-- View screenshots at each step
-- Inspect network requests
-- Debug any issues
-
-Traces are hosted and accessible via the link in the report.
-
-## Partial Reports
-
-You can generate reports even when a feature isn't complete:
-
-```bash
-$ ranger feature report
-
-Generating report...
-✅ Report generated: .ranger/reports/feat_abc123.md
-```
-
-The report will show:
-- Which items are verified
-- Which are pending
-- Which are blocked (with reasons)
-- Progress percentage
-
-This is useful for:
-- Status updates to stakeholders
-- Documenting progress before a break
-- Showing what's blocking completion

package/build/skills/feature-tracker/start.md

@@ -1,93 +0,0 @@
-# Starting a Feature Session
-
-At the START of any coding session, check if there's an existing feature to resume before creating a new one.
-
-## Resume by Git Context
-
-Features are automatically associated with the git repo and branch when created. Use `resume` to find and activate a matching feature:
-
-```bash
-ranger feature resume
-```
-
-This command:
-1. Detects current git repo URL and branch name
-2. Searches for in-progress features matching that context
-3. If found, sets it as the active feature
-4. If multiple matches, prompts you to select one
-
-## Check Current Status
-
-After resuming (or if you already have an active feature):
-
-```bash
-ranger feature show
-```
-
-This displays:
-- Feature name and ID
-- Current status (in_progress, blocked, completed)
-- Git context (repo, branch)
-- Checklist with item statuses
-
-## List Features
-
-If `resume` doesn't find a match, list all features:
-
-```bash
-ranger feature list
-```
-
-Or list features for the current branch specifically:
-
-```bash
-ranger feature list --current-branch
-```
-
-## Set Active Feature Manually
-
-If you know the feature ID:
-
-```bash
-ranger feature use feat_abc123
-```
-
-## Decision Tree
-
-```
-Start Session
-     │
-     ▼
-ranger feature resume
-     │
-     ├── Feature found? ──YES──▶ ranger feature show
-     │                                    │
-     │                                    ▼
-     │                           Continue working
-     │
-     └── No match? ──▶ ranger feature list
-                              │
-                              ├── Found one? ──▶ ranger feature use <id>
-                              │
-                              └── None exist? ──▶ See create.md
-```
-
-## Example
-
-```bash
-# Start of session
-$ ranger feature resume
-
-Searching for features matching: github.com/myorg/myapp / feature/auth...
-
-✅ Resumed feature: User Authentication (feat_abc123)
-
-🔄 User Authentication (feat_abc123)
-   Status: in_progress
-   Branch: feature/auth
-
-   Checklist:
-   1. ✅ Login flow works
-   2. ⬜ Signup creates account
-   3. ⬜ Password reset sends email
-```