update CLI references

Author: bagel897

README.md

@@ -61,14 +61,14 @@ uv tool install codegen --python 3.13
 
 # Create a codemod for a given repo
 cd path/to/repo
-codegen init
-codegen create test-function
+gs init
+gs create test-function
 
 # Run the codemod
-codegen run test-function
+gs run test-function
 
 # Create an isolated venv with codegen => open jupyter
-codegen notebook
+gs notebook
 ```
 
 ## Usage

codegen-examples/README.md

@@ -19,7 +19,7 @@ uv tool install codegen
 Initialize Codegen in your project
 
 ```bash
-codegen init
+gs init
 ```
 
 Activate the virtual environment

docs/building-with-codegen/dot-codegen.mdx

@@ -5,7 +5,7 @@ icon: "folder"
 iconType: "solid"
 ---
 
-The `.codegen` directory contains your project's Codegen configuration, codemods, and supporting files. It's automatically created when you run `codegen init`.
+The `.codegen` directory contains your project's Codegen configuration, codemods, and supporting files. It's automatically created when you run `gs init`.
 
 ## Directory Structure
 
@@ -20,10 +20,10 @@ The `.codegen` directory contains your project's Codegen configuration, codemods
 
 ## Initialization
 
-The directory is created and managed using the `codegen init` command:
+The directory is created and managed using the `gs init` command:
 
 ```bash
-codegen init [--fetch-docs] [--repo-name NAME] [--organization-name ORG]
+gs init [--fetch-docs] [--repo-name NAME] [--organization-name ORG]
 ```
 
 <Note>
@@ -40,7 +40,7 @@ Codegen maintains its own virtual environment in `.codegen/.venv/` to ensure con
 - Used for running codemods and Jupyter notebooks
 - Gitignored to avoid committing environment-specific files
 
-The environment is created during `codegen init` and used by commands like `codegen run` and `codegen notebook`.
+The environment is created during `gs init` and used by commands like `gs run` and `gs notebook`.
 
 <Note>To debug codemods, you will need to set the python virtual environment in your IDE to `.codegen/.venv`</Note>
 
@@ -78,7 +78,7 @@ Codegen automatically adds appropriate entries to your `.gitignore`:
 The `codemods/` directory is where your transformation functions live. You can create new codemods using:
 
 ```bash
-codegen create my-codemod PATH [--description "what it does"]
+gs create my-codemod PATH [--description "what it does"]
 ```
 
 This will:
@@ -87,7 +87,7 @@ This will:
 3. Set up the necessary imports and decorators
 
 <Tip>
-Use `codegen list` to see all codemods in your project.
+Use `gs list` to see all codemods in your project.
 </Tip>
 
 ## Jupyter Integration
@@ -115,12 +115,12 @@ After initializing your `.codegen` directory:
 
 1. Create your first codemod:
 ```bash
-codegen create my-codemod . -d "describe what you want to do"
+gs create my-codemod . -d "describe what you want to do"
 ```
 
 2. Run it:
 ```bash
-codegen run my-codemod --apply-local
+gs run my-codemod --apply-local
 ```
 
 3. Deploy it for team use:

docs/building-with-codegen/function-decorator.mdx

@@ -39,7 +39,7 @@ The `function` decorator is part of the codegen SDK CLI and is used to mark func
 To run a deployed function using the CLI, use the following command:
 
 ```bash
-codegen run my-function
+gs run my-function
 ```
 
 This command runs the function named `my-function`.

docs/building-with-codegen/reusable-codemods.mdx

@@ -12,7 +12,7 @@ Codegen enables you to create reusable code transformations using Python functio
 The easiest way to create a new codemod is using the CLI [create](/cli/create) command:
 
 ```bash
-codegen create rename-function .
+gs create rename-function .
 ```
 
 This creates a new codemod in your `.codegen/codemods` directory:
@@ -37,7 +37,7 @@ def run(codebase: Codebase):
 You can use AI to generate an initial implementation by providing a description:
 
 ```bash
-codegen create rename-function . -d "Rename the getUserData function to fetchUserProfile"
+gs create rename-function . -d "Rename the getUserData function to fetchUserProfile"
 ```
 
 This will:
@@ -50,7 +50,7 @@ This will:
 Once created, run your codemod using:
 
 ```bash
-codegen run rename-function
+gs run rename-function
 ```
 
 The execution flow:
@@ -104,7 +104,7 @@ def run(codebase: Codebase, arguments: RenameArgs):
 
 Run it with:
 ```bash
-codegen run rename-function --arguments '{"old_name": "getUserData", "new_name": "fetchUserProfile"}'
+gs run rename-function --arguments '{"old_name": "getUserData", "new_name": "fetchUserProfile"}'
 ```
 
 ## Directory Structure

docs/changelog/changelog.mdx

@@ -87,8 +87,8 @@ iconType: "solid"
 </Update>
 
 <Update label="v0.52.24" description="March 25, 2025">
-### [Documentation update for `codegen create` command.](https://github.com/codegen-sh/graph-sitter/releases/tag/v0.52.24)
-- Update documentation for `codegen create` command
+### [Documentation update for `gs create` command.](https://github.com/codegen-sh/graph-sitter/releases/tag/v0.52.24)
+- Update documentation for `gs create` command
 </Update>
 
 
@@ -556,7 +556,7 @@ iconType: "solid"
 
 <Update label="v0.41.0" description="February 26, 2025">
 ### [adds --daemon option and improves dataset access.](https://github.com/codegen-sh/graph-sitter/releases/tag/v0.41.0)
-- Add --daemon option to codegen run command
+- Add --daemon option to gs run command
 - Improve swebench dataset access
 </Update>
 
@@ -1312,7 +1312,7 @@ iconType: "solid"
 
 <Update label="v0.5.5" description="January 27, 2025">
 ### [Adds create flag and improves Git repository handling](https://github.com/codegen-sh/graph-sitter/releases/tag/v0.5.5)
-- Added `-d` flag to `codegen create` command
+- Added `-d` flag to `gs create` command
 - Fixed Gradio integration issues
 - Improved automatic base path detection for Git repositories
 - Enhanced codebase reset functionality to only affect SDK changes
@@ -1322,7 +1322,7 @@ iconType: "solid"
 
 <Update label="v0.5.4" description="January 27, 2025">
 ### [Adds venv management and TypeScript export support](https://github.com/codegen-sh/graph-sitter/releases/tag/v0.5.4)
-- Added virtual environment creation and persistence for `codegen init`
+- Added virtual environment creation and persistence for `gs init`
 - Added support for codebase exports in TypeScript projects
 - Reorganized test structure for better maintainability
 - Updated graph widget configuration and URLs
@@ -1334,14 +1334,14 @@ iconType: "solid"
 - Added graph widget visualization feature
 - Enhanced documentation with improved readability and new guides
 - Added system prompt functionality
-- Fixed core commands: codegen run and create
+- Fixed core commands: gs run and create
 - Various internal code cleanup and reorganization
 </Update>
 
 
 <Update label="v0.5.2" description="January 24, 2025">
 ### [Adds notebook functionality and improves documentation](https://github.com/codegen-sh/graph-sitter/releases/tag/v0.5.2)
-- Added new codegen notebook functionality
+- Added new gs notebook functionality
 - Fixed several documentation rendering issues and broken links
 - Added function call parameter documentation helpers
 - Fixed various type annotations and AST-related bugs

docs/cli/about.mdx

@@ -21,13 +21,13 @@ The graph_sitter.cli helps you:
 1. **Initialize Codegen** in your repository:
 
 ```bash
-codegen init
+gs init
 ```
 
 2. **Create your first codemod**:
 
 ```bash
-codegen create my-codemod --description "What you want to accomplish"
+gs create my-codemod --description "What you want to accomplish"
 ```
 
 The `--description` flag enables AI assistance to help generate your codemod. Be as specific as possible about what you want to achieve.

docs/cli/create.mdx

@@ -8,13 +8,13 @@ iconType: "solid"
 The `create` command generates a new codemod function with the necessary boilerplate.
 
 ```bash
-codegen create rename-function .
+gs create rename-function .
 ```
 
 ## Usage
 
 ```bash
-codegen create NAME PATH [OPTIONS]
+gs create NAME PATH [OPTIONS]
 ```
 
 ## Arguments
@@ -28,7 +28,7 @@ codegen create NAME PATH [OPTIONS]
 
 ## Generated Files
 
-When you run `codegen create rename-function .`, it creates:
+When you run `gs create rename-function .`, it creates:
 
 ```
 .codegen/
@@ -64,19 +64,19 @@ if __name__ == "__main__":
 
 Create a basic codemod:
 ```bash
-codegen create rename-function .
+gs create rename-function .
 ```
 
 Create with an AI-powered implementation:
 ```bash
-codegen create rename-function . -d "Rename the getUserData function to fetchUserProfile"
+gs create rename-function . -d "Rename the getUserData function to fetchUserProfile"
 ```
 
 ## Next Steps
 
 After creating a codemod:
 1. Edit the implementation in the generated .py file
-2. Test it with `codegen run rename-function`
+2. Test it with `gs run rename-function`
 3. Deploy it for team use with `codegen deploy rename-function`
 
 ## Common Issues

docs/cli/expert.mdx

@@ -56,6 +56,6 @@ The expert has deep knowledge of Codegen's internals and common transformation p
 
 ## Related Commands
 
-- `codegen create`: Create new codemods with AI assistance
-- `codegen run`: Execute your codemods
+- `gs create`: Create new codemods with AI assistance
+- `gs run`: Execute your codemods
 - `codegen docs-search`: Search documentation and examples

docs/cli/init.mdx

@@ -10,7 +10,7 @@ The `init` command sets up Codegen in your repository, creating necessary config
 ## Usage
 
 ```bash
-codegen init [OPTIONS]
+gs init [OPTIONS]
 ```
 
 ## Options
@@ -20,13 +20,13 @@ codegen init [OPTIONS]
 
 ## Directory Structure
 
-When you run `init`, Codegen creates a `.codegen` directory in your repository with the following structure:
+When you run `init`, gs creates a `.codegen` directory in your repository with the following structure:
 
 ```
 .codegen/
 ├── config.toml         # Configuration file with repo and org info
 ├── codemods/          # Your codemods live here
-│   └── my_codemod.py  # Created via `codegen create my-codemod`
+│   └── my_codemod.py  # Created via `gs create my-codemod`
 ├── docs/              # Local documentation for offline access
 │   ├── api/
 │   ├── examples/
@@ -47,7 +47,7 @@ This setup allows you to:
 
 ## Recommended Structure
 
-We recommend keeping your Codegen codemods in the `.codegen/codemods/` directory (this is the default when using `codegen create`). This:
+We recommend keeping your Codegen codemods in the `.codegen/codemods/` directory (this is the default when using `gs create`). This:
 
 - Keeps transformation code separate from your application code
 - Makes it easy to find and manage all your codemods
@@ -68,21 +68,21 @@ The command must be run from within a git repository. If you're not in one, you'
 ```bash
 git init
 git remote add origin <your-repo-url>
-codegen init
+gs init
 ```
 
 ## Examples
 
 Initialize with default settings (uses git repo info):
 
 ```bash
-codegen init
+gs init
 ```
 
 Initialize with custom organization and repo:
 
 ```bash
-codegen init --organization-name "my-org" --repo-name "my-project"
+gs init --organization-name "my-org" --repo-name "my-project"
 ```
 
 ## Next Steps
@@ -92,23 +92,23 @@ After initializing:
 1. Create your first codemod:
 
 ```bash
-codegen create my-function . -d "describe what you want to do"
+gs create my-function . -d "describe what you want to do"
 ```
 
 Note: The second parameter (`.`) specifies the path where the codemod should be created. This is required.
 
 2. Run it:
 
 ```bash
-codegen run my-function --apply-local
+gs run my-function --apply-local
 ```
 
 ## Updating
 
 You can run `init` again to update your local documentation and configuration:
 
 ```bash
-codegen init
+gs init
 ```
 
 This will refresh the `.codegen` directory while preserving your existing configuration.