@ranger-testing/ranger-cli 1.0.14 → 1.1.1

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
-```