@ranger-testing/ranger-cli 1.0.13 → 1.1.0

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

@@ -1,105 +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 "<comprehensive description>" \
-  --checklist "<item 1>,<item 2>,<item 3>"
-```
-
-## 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 Descriptions
-
-**The key to good feature tracking is DETAILED DESCRIPTIONS.**
-
-### Feature Names
-
-Should be clear and specific:
-
-| Bad | Good |
-|-----|------|
-| "User auth" | "User Authentication System" |
-| "Fix bug" | "Fix Payment Processing Timeout" |
-| "New feature" | "Dashboard Analytics Widget" |
-
-### Feature Descriptions
-
-Should explain the full scope and goals:
-
-**Bad:**
-```
-Login, signup, password reset
-```
-
-**Good:**
-```
-Complete user authentication system for the web app. Includes:
-- Secure login with email/password
-- New user signup with email verification
-- Password reset flow with secure tokens
-All forms should have proper validation, loading states, and error handling.
-```
-
-### Checklist Items
-
-Should explain what success looks like - these descriptions become the default task for browser verification:
-
-**Bad:**
-```
-Login works
-```
-
-**Good:**
-```
-User can log in with valid email and password - sees loading state during submission - redirects to dashboard on success - sees appropriate error message for invalid credentials
-```
-
-## Complete Example
-
-```bash
-ranger feature create "User Authentication" \
-  --description "Complete user authentication system for the web app. Includes secure login with email/password, new user signup with email verification, and password reset flow. All forms should have proper validation, loading states, and error handling." \
-  --checklist "User can log in with valid email and password - sees loading state during submission - redirects to dashboard on success - sees appropriate error message for invalid credentials,User can sign up with email and password - receives verification email - can verify email via link - account is created and user is logged in,User can request password reset - receives reset email with secure link - can set new password - can log in with new password"
-```
-
-## Output
-
-```
-Creating feature...
-
-✅ Feature created: feat_01abc123
-
-🔄 User Authentication (feat_01abc123)
-   Status: in_progress
-   Description: Complete user authentication system...
-   Repository: github.com/myorg/myapp
-   Branch: feature/auth
-   Created: 1/21/2026, 10:30:00 AM
-
-   Checklist:
-   1. ⬜ User can log in with valid email and password...
-   2. ⬜ User can sign up with email and password...
-   3. ⬜ User can request password reset...
-
-➡️  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. Add more items with `ranger feature manage --add "..."`
-3. View status with `ranger feature show`

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

@@ -1,145 +0,0 @@
-# Managing Checklist Items
-
-Manage checklist items as you work through a feature. The `manage` command supports both interactive mode (for humans) and CLI flags (for agents/automation).
-
-## Quick Reference
-
-| Action | Command |
-|--------|---------|
-| Add item | `ranger feature manage --add "description"` |
-| Edit item | `ranger feature manage --edit <index> --description "new text"` |
-| Block item | `ranger feature manage --block <index> --reason "why"` |
-| Cancel item | `ranger feature manage --cancel <index> --reason "why"` |
-| Reset to pending | `ranger feature manage --reset <index>` |
-
-**Note:** All indexes are 1-based (first item is 1, not 0).
-
-## Adding Items
-
-Add new checklist items as scope expands or you discover new requirements:
-
-```bash
-ranger feature manage --add "New item that needs to be done"
-```
-
-**Tip:** Be descriptive! The item description becomes the default task for browser verification.
-
-```bash
-# Bad
-ranger feature manage --add "Test logout"
-
-# Good
-ranger feature manage --add "User can click logout button in header - sees confirmation - is redirected to login page - session is invalidated"
-```
-
-## Editing Items
-
-Update an item's description to clarify requirements or fix typos:
-
-```bash
-ranger feature manage --edit 1 --description "Updated description with more detail"
-```
-
-Use `ranger feature show` first to see item indexes:
-
-```
-   Checklist:
-   1. ⬜ First item    <-- index 1
-   2. ⬜ Second item   <-- index 2
-   3. ⬜ Third item    <-- index 3
-```
-
-## Blocking Items
-
-Mark an item as blocked when something prevents completion:
-
-```bash
-ranger feature manage --block 2 --reason "API endpoint not implemented yet"
-```
-
-Common blocking reasons:
-- Bug in dependent system
-- Missing API endpoint
-- Waiting for design assets
-- Environment issue
-
-## Canceling Items
-
-Cancel items that are no longer needed:
-
-```bash
-ranger feature manage --cancel 3 --reason "Descoped to v2 based on PM feedback"
-```
-
-Canceled items:
-- Don't count toward completion
-- Are shown with strikethrough in reports
-- Preserve the cancellation reason for context
-
-## Resetting Items
-
-Reset a blocked or canceled item back to pending:
-
-```bash
-ranger feature manage --reset 2
-```
-
-Use this when:
-- A blocker is resolved
-- A canceled item is back in scope
-- You need to re-verify a previously verified item
-
-## Interactive Mode
-
-For humans, run without flags to get an interactive menu:
-
-```bash
-ranger feature manage
-```
-
-This shows:
-```
-Managing: User Authentication (feat_abc123)
-
-Current checklist:
-1. ✅ Login flow works
-2. ⬜ Signup creates account
-3. 🛑 Password reset sends email
-   Blocked: Email service not configured
-
-? What would you like to do?
-❯ Add new item
-  Update existing item
-  Cancel
-```
-
-## Item Statuses
-
-| Status | Emoji | Meaning |
-|--------|-------|---------|
-| Pending | ⬜ | Not yet verified |
-| Verified | ✅ | Successfully verified in browser |
-| Blocked | 🛑 | Cannot complete due to blocker |
-| Canceled | ⛔ | No longer needed |
-
-## Workflow Example
-
-```bash
-# Check current state
-ranger feature show
-
-# Add a new requirement discovered during implementation
-ranger feature manage --add "Form should show inline validation errors"
-
-# Realize an item needs clarification
-ranger feature manage --edit 2 --description "Signup form validates email format and password strength before submission"
-
-# Hit a blocker
-ranger feature manage --block 3 --reason "SMTP server not configured in local env"
-
-# Blocker resolved later
-ranger feature manage --reset 3
-
-# Scope change from PM
-ranger feature manage --cancel 4 --reason "Social login moved to v2"
-```

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 Active Features
-
-If `resume` doesn't find a match, list all active features:
-
-```bash
-ranger feature list --status in_progress
-```
-
-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 --status in_progress
-                              │
-                              ├── 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
-```