@ranger-testing/ranger-cli 1.0.13 → 1.0.14

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

@@ -5,11 +5,11 @@ After implementing code for a checklist item, verify it works in the browser. Th
 ## Basic Command
 
 ```bash
-ranger verify-feature \
-  --url "<starting url>" \
-  --task "<what to verify>"
+ranger verify-feature --task "<what to verify>"
 ```
 
+The URL is derived from your active environment's `baseUrl` setting.
+
 ## Required: Active Feature
 
 `verify-feature` requires an active feature. If you don't have one:
@@ -31,10 +31,9 @@ ranger feature use <id>
 
 | Option | Required | Description |
 |--------|----------|-------------|
-| `--url` | Yes | Starting URL for the verification |
+| `--env` | No | Environment to use (defaults to active environment) |
 | `--task` | No | What to verify (defaults to item description) |
 | `--item` | No | Item index to verify (skips selection prompt) |
-| `--new-item` | No | Create and verify a new item |
 
 ## Writing Good Task Descriptions
 
@@ -56,7 +55,7 @@ If your checklist item has a detailed description, you can omit `--task`:
 
 ```bash
 # Item 1: "User can log in with valid credentials - sees loading state - redirects to dashboard"
-ranger verify-feature --url "http://localhost:3000/login" --item 1
+ranger verify-feature --item 1
 ```
 
 The item's description becomes the task automatically.
@@ -78,7 +77,6 @@ After verification, the agent evaluates if the result satisfies the checklist it
 
 ```bash
 ranger verify-feature \
-  --url "http://localhost:3000/login" \
   --task "Log in with test@example.com / password123, verify redirect to dashboard"
 ```
 
@@ -87,19 +85,17 @@ ranger verify-feature \
 ```bash
 # Skip the selection prompt, verify item 2 directly
 ranger verify-feature \
-  --url "http://localhost:3000/signup" \
   --task "Complete signup flow with new email" \
   --item 2
 ```
 
-### Create and Verify New Item
+### Verify with Specific Environment
 
 ```bash
-# Add a new checklist item and verify it in one command
+# Use staging environment instead of active environment
 ranger verify-feature \
-  --url "http://localhost:3000/settings" \
-  --task "Change profile photo and verify it updates" \
-  --new-item "User can update profile photo from settings page"
+  --env staging \
+  --task "Verify login works in staging"
 ```
 
 ## After Verification
@@ -140,4 +136,4 @@ Run `ranger use <env-name>` to set an environment with browser access.
 The agent has 59 minutes max. For very long flows, break into smaller checklist items.
 
 ### Wrong item marked
-Use `ranger feature manage --reset <index>` to reset an item, then re-verify.
+Reset the item via the dashboard, then re-verify.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@ranger-testing/ranger-cli",
-    "version": "1.0.13",
+    "version": "1.0.14",
     "type": "module",
     "bin": {
         "ranger": "./build/cli.js",
@@ -10,10 +10,12 @@
         "build": "tsc && npm run obfuscate && cp -r src/skills build/ && chmod 755 build/cli.js",
         "obfuscate": "node scripts/obfuscate.cjs",
         "dev": "tsx src/cli.ts",
-        "check-playwright-version": "node scripts/check-playwright-version.cjs"
+        "check-playwright-version": "node scripts/check-playwright-version.cjs",
+        "postinstall": "node scripts/postinstall.js"
     },
     "files": [
-        "build"
+        "build",
+        "scripts/postinstall.js"
     ],
     "dependencies": {
         "@anthropic-ai/claude-agent-sdk": "^0.1.0",

package/scripts/postinstall.js

@@ -0,0 +1,18 @@
+#!/usr/bin/env node
+
+/**
+ * Postinstall script for @ranger-testing/ranger-cli
+ * Displays welcome message and setup instructions after npm install
+ */
+
+console.log(`
+🏞️ Ranger CLI installed!
+
+Get started:
+  1. Get your API token: https://dashboard.ranger.net/cli
+  2. Run: ranger start <your-token>
+
+For Claude Code, install the plugin in Claude Code:
+  /plugin marketplace add ranger-testing/trailhead
+  /plugin install ranger@trailhead
+`);

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