Rename corpus:view to just corpus.

Author: nedtwigg

.claude/agents/corpus-fixer.md

@@ -1,16 +1,16 @@
 ---
 name: corpus-fixer
-description: Use this agent when you need to fix or improve the detection logic for a specific Gitcasso corpus by testing changes in the corpus:view development environment. Examples: <example>Context: User has identified issues with comment spot detection in a specific corpus and wants to test fixes. user: 'The comment detection is missing some spots in corpus ABC123, can you help fix the enhancer logic?' assistant: 'I'll use the corpus-fixer agent to investigate and fix the detection issues in that corpus.' <commentary>Since the user wants to fix detection logic for a specific corpus, use the corpus-fixer agent to run the corpus:view environment and test changes.</commentary></example> <example>Context: User wants to validate that recent changes to an enhancer are working correctly. user: 'I made some changes to the GitHub enhancer, can you test it against corpus XYZ789?' assistant: 'Let me use the corpus-fixer agent to test your enhancer changes against that specific corpus.' <commentary>The user wants to test enhancer changes against a specific corpus, so use the corpus-fixer agent to validate the changes in the corpus:view environment.</commentary></example>
+description: Use this agent when you need to fix or improve the detection logic for a specific Gitcasso corpus by testing changes in the corpus development environment. Examples: <example>Context: User has identified issues with comment spot detection in a specific corpus and wants to test fixes. user: 'The comment detection is missing some spots in corpus ABC123, can you help fix the enhancer logic?' assistant: 'I'll use the corpus-fixer agent to investigate and fix the detection issues in that corpus.' <commentary>Since the user wants to fix detection logic for a specific corpus, use the corpus-fixer agent to run the corpus environment and test changes.</commentary></example> <example>Context: User wants to validate that recent changes to an enhancer are working correctly. user: 'I made some changes to the GitHub enhancer, can you test it against corpus XYZ789?' assistant: 'Let me use the corpus-fixer agent to test your enhancer changes against that specific corpus.' <commentary>The user wants to test enhancer changes against a specific corpus, so use the corpus-fixer agent to validate the changes in the corpus environment.</commentary></example>
 model: inherit
 ---
 
-You are an expert Gitcasso corpus debugging specialist with deep knowledge of browser extension development. You operate within the root project directory and specialize in using the corpus:view development environment to diagnose and fix detection logic issues.
+You are an expert Gitcasso corpus debugging specialist with deep knowledge of browser extension development. You operate within the root project directory and specialize in using the corpus development environment to diagnose and fix detection logic issues.
 
 Your primary workflow:
 
 1. **Environment Setup**: Always start by reading the documentation at the top of the `corpus-view.ts` file to understand the dev environment.
 
-2. **Launch Development Environment**: Execute `pnpm corpus:view` to bring up the corpus:view development environment. Ensure the environment starts successfully before proceeding.
+2. **Launch Development Environment**: Execute `pnpm corpus` to bring up the corpus development environment. Ensure the environment starts successfully before proceeding.
 
 3. **Browser Navigation**: Use the Playwright MCP to interact with the development environment. Navigate to the specific Gitcasso corpus that needs investigation or fixing.
 

.claude/commands/corpus-loop.md

@@ -1,6 +1,6 @@
 ---
 argument-hint: [corpus_slug]
-description: uses Playwright MCP and the `corpus:view` to parse page elements
+description: uses Playwright MCP and the `corpus` to parse page elements
 ---
 
 - using Playwright MCP, navigate to `http://localhost:3001/corpus/$1/gitcasso`

CONTRIBUTING.md

@@ -79,7 +79,7 @@ When the `textarea` gets removed from the page, the `TextareaRegistry` is notifi
 ## Testing
 
 - `pnpm playground` gives you a test environment where you can tinker with the popup with various test data, supports hot reload
-- `pnpm corpus:view` gives you recordings of various web pages which you can see with and without enhancement by the browser extension
+- `pnpm corpus` gives you recordings of various web pages which you can see with and without enhancement by the browser extension
 
 ### Test Corpus
 
@@ -114,7 +114,7 @@ We maintain a corpus of test pages in two formats for testing the browser extens
 
 #### Viewing Corpus Files
 
-- Run `pnpm corpus:view` to start the test server at http://localhost:3001
+- Run `pnpm corpus` to start the test server at http://localhost:3001
 - Select any corpus file to view in two modes:
   - **Clean**: Original page without extension
   - **Gitcasso**: Page with extension injected for testing

package.json

@@ -64,7 +64,7 @@
     "playground": "vite --config vite.playground.config.ts",
     "playground:build": "vite build --config vite.playground.config.ts",
     "corpus:har:record": "tsx tests/corpus-har-record.ts",
-    "corpus:view": "tsx tests/corpus-view.ts"
+    "corpus": "tsx tests/corpus-view.ts"
   },
   "type": "module",
   "version": "0.0.1"