codebase-extractor 1.1.0__tar.gz → 1.2.0__tar.gz

{codebase_extractor-1.1.0/src/codebase_extractor.egg-info → codebase_extractor-1.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codebase-extractor
-Version: 1.1.0
+Version: 1.2.0
 Summary: A CLI tool to extract project source code into structured Markdown files for LLM & AI context.
 Author: Lukasz Lekowski
 Project-URL: Homepage, https://github.com/lukaszlekowski/codebase-extractor
@@ -10,7 +10,7 @@ Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Classifier: Topic :: Software Development :: Documentation
 Classifier: Topic :: Utilities
-Requires-Python: >=3.9
+Requires-Python: >=3.14
 Description-Content-Type: text/markdown
 License-File: LICENCE
 Requires-Dist: questionary
@@ -75,12 +75,12 @@ The tool is highly configurable, allowing you to select specific folders, exclud
 ## ✨ Key Features
 
 - **Interactive & User-Friendly:** A guided, multi-step CLI experience that makes selecting options simple and clear.
+- **Quick Start by Default:** The tool starts without delay. Detailed instructions are available via an `--instructions` flag when you need a reminder.
 - **Smart Filtering:** Automatically excludes common dependency folders, build artifacts, version control directories, and IDE configuration files. The exact filters are configurable.
 - **Flexible Selection Modes:** Choose to extract the entire project with one command, or dive into a specific selection mode.
-- **🌳 Nested Folder Selection:** Interactively browse and select specific sub-folders from a tree-like view.
+- **🌳 Visual Tree Selection:** Interactively browse and select specific sub-folders from a clear, pipe-based tree structure.
 - **🔢 Configurable Scan Depth:** You decide how many levels deep the script should look for folders when building the selection tree.
-- **YAML Metadata:** Each generated Markdown file is prepended with a YAML front matter block containing useful metadata like a unique run ID, timestamp, and file count for easy tracking and parsing.
-- **🚀 Quick Start Mode:** Use the `--no-instructions` flag to skip the detailed intro guide on subsequent runs.
+- **Rich YAML Metadata:** Each generated Markdown file is prepended with a YAML front matter block containing useful metadata like a unique run ID, timestamp, file count, character count, and word count.
 - **Safe & Robust:** Features graceful exit handling (`Ctrl+C`) and provides clear feedback during the extraction process.
 
 ---
@@ -165,15 +165,15 @@ pipx install codebase-extractor
 Once installed, you can run the tool from any terminal window. Navigate to your project's root directory and run the command:
 
 ```bash
-code-extractor
+codebase-extractor
 ```
 
-The script will then guide you through the extraction process.
+The script will launch immediately and guide you through the extraction process.
 
-For repeat usage, you can skip the detailed introductory guide by using the `--no-instructions` or `-ni` flag:
+For a detailed guide on how the script works, you can use the `--instructions` flag:
 
 ```bash
-code-extractor --no-instructions
+codebase-extractor --instructions
 ```
 
 ### The Process
@@ -193,25 +193,25 @@ The tool will guide you through a series of prompts:
 
 ### Output Details
 
-All output files are saved in a `CODEBASE_EXTRACTS` directory within your project folder. Each generated Markdown file includes a YAML metadata header with a unique reference ID, timestamp, and file count for easy tracking and parsing.
+All output files are saved in a `CODEBASE_EXTRACTS` directory within your project folder. Each generated Markdown file includes a YAML metadata header with a unique reference ID, timestamp, file count, character count, and word count for easy tracking and parsing.
 
 ### ⚡ CLI Command Reference
 
 For non-interactive use and automation, you can control the script entirely with these arguments.
 
-| Argument                   | Description                                                                  | Default Value               |
-| :------------------------- | :--------------------------------------------------------------------------- | :-------------------------- |
-| `-ni`, `--no-instructions` | Run the script without printing the detailed instruction banner.             | `False`                     |
-| `--root <path>`            | The root directory of the project to extract.                                | The current directory       |
-| `--output-dir <name>`      | Custom name for the output directory.                                        | `CODEBASE_EXTRACTS`         |
-| `--dry-run`                | Simulate the extraction process without writing any files.                   | `False`                     |
-| `-v`, `--verbose`          | Enable verbose logging for debugging.                                        | `False`                     |
-| `--log-file <path>`        | Path to save the log file.                                                   | `None`                      |
-| `--exclude-large-files`    | Non-interactive: Exclude files larger than 1MB.                              | `False`                     |
-| `--mode <mode>`            | Non-interactive: Set the extraction mode. Choices: `everything`, `specific`. | `None` (Interactive prompt) |
-| `--depth <number>`         | Non-interactive: Set the folder scan depth for 'specific' mode.              | `3`                         |
-| `--select-folders <list>`  | Non-interactive: A space-separated list of folders/sub-folders to extract.   | `[]`                        |
-| `--select-root`            | Non-interactive: Include files from the root directory in the extraction.    | `False`                     |
+| Argument                  | Description                                                                  | Default Value               |
+| :------------------------ | :--------------------------------------------------------------------------- | :-------------------------- |
+| `--instructions`          | Show the detailed instruction guide on startup.                              | `False`                     |
+| `--root <path>`           | The root directory of the project to extract.                                | The current directory       |
+| `--output-dir <name>`     | Custom name for the output directory.                                        | `CODEBASE_EXTRACTS`         |
+| `--dry-run`               | Simulate the extraction process without writing any files.                   | `False`                     |
+| `-v`, `--verbose`         | Enable verbose logging for debugging.                                        | `False`                     |
+| `--log-file <path>`       | Path to save the log file.                                                   | `None`                      |
+| `--exclude-large-files`   | Non-interactive: Exclude files larger than 1MB.                              | `False`                     |
+| `--mode <mode>`           | Non-interactive: Set the extraction mode. Choices: `everything`, `specific`. | `None` (Interactive prompt) |
+| `--depth <number>`        | Non-interactive: Set the folder scan depth for 'specific' mode.              | `3`                         |
+| `--select-folders <list>` | Non-interactive: A space-separated list of folders/sub-folders to extract.   | `[]`                        |
+| `--select-root`           | Non-interactive: Include files from the root directory in the extraction.    | `False`                     |
 
 ---
 
@@ -224,7 +224,7 @@ Here are a few practical examples of how to use the tool from your command line.
   A common command for quick, automated runs.
 
   ```bash
-  code-extractor --no-instructions --mode everything
+  codebase-extractor --mode everything
   ```
 
 - #### Extract specific sub-folders non-interactively
@@ -232,7 +232,7 @@ Here are a few practical examples of how to use the tool from your command line.
   This command extracts only the `src/components` and `src/hooks` directories, plus any files in the root.
 
   ```bash
-  code-extractor --ni --mode specific --select-folders src/components src/hooks --select-root
+  codebase-extractor --mode specific --select-folders src/components src/hooks --select-root
   ```
 
 - #### Perform a safe dry run
@@ -240,13 +240,13 @@ Here are a few practical examples of how to use the tool from your command line.
   This will simulate a full extraction and print what it _would_ have done, without creating any files.
 
   ```bash
-  code-extractor --dry-run --mode everything
+  codebase-extractor --dry-run --mode everything
   ```
 
 - #### Run on a different project and save to a custom folder
   This targets a completely different directory and specifies a custom output folder name.
   ```bash
-  code-extractor --root /path/to/another/project --output-dir MyProject_Extraction
+  codebase-extractor --root /path/to/another/project --output-dir MyProject_Extraction
   ```
 
 ---
@@ -256,10 +256,11 @@ Here are a few practical examples of how to use the tool from your command line.
 The tool uses a set of rules to determine which files and folders to include in the extraction. Here are the default settings found in the `config.py` file.
 
 <details>
-  <summary><strong>Click to view Excluded Directories</strong></summary>
+<summary><strong>Click to view Excluded Directories</strong></summary>
   
   - `node_modules`, `vendor`, `__pycache__`, `dist`, `build`, `target`, `.next`
   - `.git`, `.svn`, `.hg`, `.vscode`, `.idea`, `venv`, `.venv`
+  - `.dart_tool`, `.gradle`, `Pods`, `DerivedData`
   
 </details>
 
@@ -273,17 +274,20 @@ The tool uses a set of rules to determine which files and folders to include in
 <details>
   <summary><strong>Click to view Allowed Filenames & Extensions</strong></summary>
   
-  The script will process any file with one of the following extensions. It also explicitly allows common configuration files that may not have an extension.
+The script will process any file with one of the following extensions. It also explicitly allows common configuration files that may not have an extension.
   
   **Allowed Filenames:**
-  - `dockerfile`, `.gitignore`, `.htaccess`, `makefile`
+  - `dockerfile`, `.gitignore`, `.htaccess`, `makefile`, `.dockerignore`, `.env.example`
+  - `podfile`, `gemfile`, `jenkinsfile`, `gradlew`
   
   **Allowed Extensions:**
-  - `.php`, `.html`, `.css`, `.js`, `.jsx`, `.ts`, `.tsx`, `.vue`, `.svelte`
-  - `.py`, `.rb`, `.java`, `.c`, `.cpp`, `.cs`, `.go`, `.rs`
-  - `.json`, `.xml`, `.yaml`, `.yml`, `.toml`, `.ini`, `.conf`
-  - `.md`, `.txt`, `.rst`, `.twig`, `.blade`, `.handlebars`, `.mustache`, `.ejs`
-  - `.sql`, `.graphql`, `.gql`, `.tf`
+  - **Web & General:** `.php`, `.html`, `.css`, `.js`, `.jsx`, `.ts`, `.tsx`, `.vue`, `.svelte`
+  - **Backend & Systems:** `.py`, `.rb`, `.java`, `.c`, `.cpp`, `.cs`, `.go`, `.rs`
+  - **Config & Data:** `.json`, `.xml`, `.yaml`, `.yml`, `.toml`, `.ini`, `.conf`
+  - **Docs & Templates:** `.md`, `.txt`, `.rst`, `.twig`, `.blade`, `.handlebars`, `.mustache`, `.ejs`
+  - **Database & IaC:** `.sql`, `.graphql`, `.gql`, `.tf`
+  - **Mobile (Flutter, Android, iOS):** `.dart`, `.arb`, `.gradle`, `.properties`, `.plist`, `.xcconfig`
+  - **Scripts:** `.sh`, `.bat`
   
 </details>
 
@@ -291,7 +295,7 @@ The tool uses a set of rules to determine which files and folders to include in
 
 ## 🤔 Troubleshooting
 
-- **Problem:** After installation, I run `code-extractor` and my terminal says `command not found`.
+- **Problem:** After installation, I run `codebase-extractor` and my terminal says `command not found`.
 - **Solution:** This is usually a `PATH` issue. It means your system's shell doesn't know where to find the installed script. The `pip install --user` command sometimes requires you to add a local scripts directory to your `PATH`. Please refer to your operating system's documentation for instructions on how to modify your `PATH` environment variable.
 
 - **Problem:** The tool ran, but a specific folder or file I expected to see is missing from the output.

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0}/README.md

@@ -55,12 +55,12 @@ The tool is highly configurable, allowing you to select specific folders, exclud
 ## ✨ Key Features
 
 - **Interactive & User-Friendly:** A guided, multi-step CLI experience that makes selecting options simple and clear.
+- **Quick Start by Default:** The tool starts without delay. Detailed instructions are available via an `--instructions` flag when you need a reminder.
 - **Smart Filtering:** Automatically excludes common dependency folders, build artifacts, version control directories, and IDE configuration files. The exact filters are configurable.
 - **Flexible Selection Modes:** Choose to extract the entire project with one command, or dive into a specific selection mode.
-- **🌳 Nested Folder Selection:** Interactively browse and select specific sub-folders from a tree-like view.
+- **🌳 Visual Tree Selection:** Interactively browse and select specific sub-folders from a clear, pipe-based tree structure.
 - **🔢 Configurable Scan Depth:** You decide how many levels deep the script should look for folders when building the selection tree.
-- **YAML Metadata:** Each generated Markdown file is prepended with a YAML front matter block containing useful metadata like a unique run ID, timestamp, and file count for easy tracking and parsing.
-- **🚀 Quick Start Mode:** Use the `--no-instructions` flag to skip the detailed intro guide on subsequent runs.
+- **Rich YAML Metadata:** Each generated Markdown file is prepended with a YAML front matter block containing useful metadata like a unique run ID, timestamp, file count, character count, and word count.
 - **Safe & Robust:** Features graceful exit handling (`Ctrl+C`) and provides clear feedback during the extraction process.
 
 ---
@@ -145,15 +145,15 @@ pipx install codebase-extractor
 Once installed, you can run the tool from any terminal window. Navigate to your project's root directory and run the command:
 
 ```bash
-code-extractor
+codebase-extractor
 ```
 
-The script will then guide you through the extraction process.
+The script will launch immediately and guide you through the extraction process.
 
-For repeat usage, you can skip the detailed introductory guide by using the `--no-instructions` or `-ni` flag:
+For a detailed guide on how the script works, you can use the `--instructions` flag:
 
 ```bash
-code-extractor --no-instructions
+codebase-extractor --instructions
 ```
 
 ### The Process
@@ -173,25 +173,25 @@ The tool will guide you through a series of prompts:
 
 ### Output Details
 
-All output files are saved in a `CODEBASE_EXTRACTS` directory within your project folder. Each generated Markdown file includes a YAML metadata header with a unique reference ID, timestamp, and file count for easy tracking and parsing.
+All output files are saved in a `CODEBASE_EXTRACTS` directory within your project folder. Each generated Markdown file includes a YAML metadata header with a unique reference ID, timestamp, file count, character count, and word count for easy tracking and parsing.
 
 ### ⚡ CLI Command Reference
 
 For non-interactive use and automation, you can control the script entirely with these arguments.
 
-| Argument                   | Description                                                                  | Default Value               |
-| :------------------------- | :--------------------------------------------------------------------------- | :-------------------------- |
-| `-ni`, `--no-instructions` | Run the script without printing the detailed instruction banner.             | `False`                     |
-| `--root <path>`            | The root directory of the project to extract.                                | The current directory       |
-| `--output-dir <name>`      | Custom name for the output directory.                                        | `CODEBASE_EXTRACTS`         |
-| `--dry-run`                | Simulate the extraction process without writing any files.                   | `False`                     |
-| `-v`, `--verbose`          | Enable verbose logging for debugging.                                        | `False`                     |
-| `--log-file <path>`        | Path to save the log file.                                                   | `None`                      |
-| `--exclude-large-files`    | Non-interactive: Exclude files larger than 1MB.                              | `False`                     |
-| `--mode <mode>`            | Non-interactive: Set the extraction mode. Choices: `everything`, `specific`. | `None` (Interactive prompt) |
-| `--depth <number>`         | Non-interactive: Set the folder scan depth for 'specific' mode.              | `3`                         |
-| `--select-folders <list>`  | Non-interactive: A space-separated list of folders/sub-folders to extract.   | `[]`                        |
-| `--select-root`            | Non-interactive: Include files from the root directory in the extraction.    | `False`                     |
+| Argument                  | Description                                                                  | Default Value               |
+| :------------------------ | :--------------------------------------------------------------------------- | :-------------------------- |
+| `--instructions`          | Show the detailed instruction guide on startup.                              | `False`                     |
+| `--root <path>`           | The root directory of the project to extract.                                | The current directory       |
+| `--output-dir <name>`     | Custom name for the output directory.                                        | `CODEBASE_EXTRACTS`         |
+| `--dry-run`               | Simulate the extraction process without writing any files.                   | `False`                     |
+| `-v`, `--verbose`         | Enable verbose logging for debugging.                                        | `False`                     |
+| `--log-file <path>`       | Path to save the log file.                                                   | `None`                      |
+| `--exclude-large-files`   | Non-interactive: Exclude files larger than 1MB.                              | `False`                     |
+| `--mode <mode>`           | Non-interactive: Set the extraction mode. Choices: `everything`, `specific`. | `None` (Interactive prompt) |
+| `--depth <number>`        | Non-interactive: Set the folder scan depth for 'specific' mode.              | `3`                         |
+| `--select-folders <list>` | Non-interactive: A space-separated list of folders/sub-folders to extract.   | `[]`                        |
+| `--select-root`           | Non-interactive: Include files from the root directory in the extraction.    | `False`                     |
 
 ---
 
@@ -204,7 +204,7 @@ Here are a few practical examples of how to use the tool from your command line.
   A common command for quick, automated runs.
 
   ```bash
-  code-extractor --no-instructions --mode everything
+  codebase-extractor --mode everything
   ```
 
 - #### Extract specific sub-folders non-interactively
@@ -212,7 +212,7 @@ Here are a few practical examples of how to use the tool from your command line.
   This command extracts only the `src/components` and `src/hooks` directories, plus any files in the root.
 
   ```bash
-  code-extractor --ni --mode specific --select-folders src/components src/hooks --select-root
+  codebase-extractor --mode specific --select-folders src/components src/hooks --select-root
   ```
 
 - #### Perform a safe dry run
@@ -220,13 +220,13 @@ Here are a few practical examples of how to use the tool from your command line.
   This will simulate a full extraction and print what it _would_ have done, without creating any files.
 
   ```bash
-  code-extractor --dry-run --mode everything
+  codebase-extractor --dry-run --mode everything
   ```
 
 - #### Run on a different project and save to a custom folder
   This targets a completely different directory and specifies a custom output folder name.
   ```bash
-  code-extractor --root /path/to/another/project --output-dir MyProject_Extraction
+  codebase-extractor --root /path/to/another/project --output-dir MyProject_Extraction
   ```
 
 ---
@@ -236,10 +236,11 @@ Here are a few practical examples of how to use the tool from your command line.
 The tool uses a set of rules to determine which files and folders to include in the extraction. Here are the default settings found in the `config.py` file.
 
 <details>
-  <summary><strong>Click to view Excluded Directories</strong></summary>
+<summary><strong>Click to view Excluded Directories</strong></summary>
   
   - `node_modules`, `vendor`, `__pycache__`, `dist`, `build`, `target`, `.next`
   - `.git`, `.svn`, `.hg`, `.vscode`, `.idea`, `venv`, `.venv`
+  - `.dart_tool`, `.gradle`, `Pods`, `DerivedData`
   
 </details>
 
@@ -253,17 +254,20 @@ The tool uses a set of rules to determine which files and folders to include in
 <details>
   <summary><strong>Click to view Allowed Filenames & Extensions</strong></summary>
   
-  The script will process any file with one of the following extensions. It also explicitly allows common configuration files that may not have an extension.
+The script will process any file with one of the following extensions. It also explicitly allows common configuration files that may not have an extension.
   
   **Allowed Filenames:**
-  - `dockerfile`, `.gitignore`, `.htaccess`, `makefile`
+  - `dockerfile`, `.gitignore`, `.htaccess`, `makefile`, `.dockerignore`, `.env.example`
+  - `podfile`, `gemfile`, `jenkinsfile`, `gradlew`
   
   **Allowed Extensions:**
-  - `.php`, `.html`, `.css`, `.js`, `.jsx`, `.ts`, `.tsx`, `.vue`, `.svelte`
-  - `.py`, `.rb`, `.java`, `.c`, `.cpp`, `.cs`, `.go`, `.rs`
-  - `.json`, `.xml`, `.yaml`, `.yml`, `.toml`, `.ini`, `.conf`
-  - `.md`, `.txt`, `.rst`, `.twig`, `.blade`, `.handlebars`, `.mustache`, `.ejs`
-  - `.sql`, `.graphql`, `.gql`, `.tf`
+  - **Web & General:** `.php`, `.html`, `.css`, `.js`, `.jsx`, `.ts`, `.tsx`, `.vue`, `.svelte`
+  - **Backend & Systems:** `.py`, `.rb`, `.java`, `.c`, `.cpp`, `.cs`, `.go`, `.rs`
+  - **Config & Data:** `.json`, `.xml`, `.yaml`, `.yml`, `.toml`, `.ini`, `.conf`
+  - **Docs & Templates:** `.md`, `.txt`, `.rst`, `.twig`, `.blade`, `.handlebars`, `.mustache`, `.ejs`
+  - **Database & IaC:** `.sql`, `.graphql`, `.gql`, `.tf`
+  - **Mobile (Flutter, Android, iOS):** `.dart`, `.arb`, `.gradle`, `.properties`, `.plist`, `.xcconfig`
+  - **Scripts:** `.sh`, `.bat`
   
 </details>
 
@@ -271,7 +275,7 @@ The tool uses a set of rules to determine which files and folders to include in
 
 ## 🤔 Troubleshooting
 
-- **Problem:** After installation, I run `code-extractor` and my terminal says `command not found`.
+- **Problem:** After installation, I run `codebase-extractor` and my terminal says `command not found`.
 - **Solution:** This is usually a `PATH` issue. It means your system's shell doesn't know where to find the installed script. The `pip install --user` command sometimes requires you to add a local scripts directory to your `PATH`. Please refer to your operating system's documentation for instructions on how to modify your `PATH` environment variable.
 
 - **Problem:** The tool ran, but a specific folder or file I expected to see is missing from the output.

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0}/pyproject.toml

@@ -4,14 +4,14 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "codebase-extractor"
-version = "1.1.0"
+version = "1.2.0"
 authors = [
   { name="Lukasz Lekowski" },
 ]
 description = "A CLI tool to extract project source code into structured Markdown files for LLM & AI context."
 readme = "README.md"
 license = { file="LICENSE" }
-requires-python = ">=3.9"
+requires-python = ">=3.14"
 classifiers = [
     "Programming Language :: Python :: 3",
     "License :: OSI Approved :: MIT License",
@@ -27,7 +27,7 @@ dependencies = [
 
 # This creates the `code-extractor` command in the user's terminal
 [project.scripts]
-code-extractor = "codebase_extractor.main_logic:main"
+codebase-extractor = "codebase_extractor.main_logic:main"
 
 [project.urls]
 "Homepage" = "https://github.com/lukaszlekowski/codebase-extractor"

codebase_extractor-1.2.0/src/codebase_extractor/__init__.py

@@ -0,0 +1 @@
+__version__ = "1.2.0"

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0}/src/codebase_extractor/cli.py

@@ -10,9 +10,10 @@ def parse_arguments():
     
     # General Flags
     parser.add_argument(
-        '-ni', '--no-instructions',
+        '--instructions',
         action='store_true',
-        help="Run the script without printing the detailed instruction banner."
+        default=False,  # ADDED: This ensures the attribute always exists.
+        help="Show the detailed instruction guide on startup."
     )
     parser.add_argument(
         '--root',

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0}/src/codebase_extractor/config.py

@@ -10,30 +10,62 @@ OUTPUT_DIR_NAME = "CODEBASE_EXTRACTS"
 
 # --- FILE/FOLDER LISTS ---
 EXCLUDED_DIRS = {
+    # Standard exclusions
     "node_modules", "vendor", "__pycache__", "dist", "build", "target", ".next",
-    ".git", ".svn", ".hg", ".vscode", ".idea", "venv", ".venv",
+    ".git", ".svn", ".hg", ".vscode", ".idea", "venv", ".venv", ".dart_tool",
+    # Flutter & Mobile specific exclusions
+    ".dart_tool",  # Critical: Contains noisy build config
+    ".gradle",     # Internal Gradle cache
+    "Pods",        # iOS external dependencies
+    "DerivedData", # iOS build artifacts
 }
 EXCLUDED_FILENAMES = {
-    "package-lock.json", "yarn.lock", "composer.lock", ".env"
+    "package-lock.json", "yarn.lock", "composer.lock", ".env", "Podfile.lock",
 }
 ALLOWED_FILENAMES = {
-    "dockerfile", ".gitignore", ".htaccess", "makefile"
+# General
+    "dockerfile", ".gitignore", ".htaccess", "makefile", ".dockerignore", ".env.example",
+    # Mobile
+    "podfile", "gemfile", "jenkinsfile", "gradlew",
 }
 ALLOWED_EXTENSIONS = {
+# Web & General
     ".php", ".html", ".css", ".js", ".jsx", ".ts", ".tsx", ".vue", ".svelte",
     ".py", ".rb", ".java", ".c", ".cpp", ".cs", ".go", ".rs", ".json", ".xml",
     ".yaml", ".yml", ".toml", ".ini", ".conf", ".md", ".txt", ".rst", ".twig",
     ".blade", ".handlebars", ".mustache", ".ejs", ".sql", ".graphql", ".gql", ".tf",
+    
+    # Flutter / Dart
+    ".dart", ".arb",
+    
+    # Android
+    ".gradle", ".properties",
+    
+    # iOS
+    ".plist", ".xcconfig",
+    
+    # Scripts
+    ".sh", ".bat",
 }
 
 # --- MAPPINGS & CONSTANTS ---
 EXTENSION_LANG_MAP = {
+    # Web & General
     ".js": "javascript", ".ts": "typescript", ".tsx": "tsx", ".py": "python",
     ".html": "html", ".css": "css", ".json": "json", ".md": "markdown", ".txt": "",
     ".sh": "bash", ".yml": "yaml", ".yaml": "yaml", ".php": "php", ".rb": "ruby",
     ".java": "java", ".c": "c", ".cpp": "cpp", ".cs": "csharp", ".go": "go",
     ".rs": "rust", ".vue": "vue", ".svelte": "svelte", ".sql": "sql",
     ".graphql": "graphql", ".gql": "graphql",
+    
+    # Mobile Specific
+    ".dart": "dart",
+    ".gradle": "groovy",
+    ".plist": "xml",
+    ".xcconfig": "properties",
+    ".properties": "properties",
+    ".arb": "json",
+    ".bat": "batch",
 }
 MAX_FILE_SIZE_MB = 1
 FILE_COUNT_WARNING_THRESHOLD = 1000

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0}/src/codebase_extractor/file_handler.py

@@ -10,29 +10,46 @@ import questionary
 
 
 def get_folder_choices(root_path: Path, max_depth: int) -> list:
-    """Recursively finds folders up to a max depth and prepares them for questionary."""
+    """Recursively finds folders up to a max depth and prepares them for questionary with a visual tree."""
     choices = []
-    
-    def scanner(current_path: Path, depth: int):
+
+    def scanner(current_path: Path, prefix: str, depth: int):
+        """A recursive helper to build the folder tree."""
+        # Stop scanning if the maximum depth is reached
         if depth > max_depth:
             return
             
-        relative_path = current_path.relative_to(root_path)
-        prefix = "  " * (depth - 1)
-        display_name = f"{prefix}{current_path.name}"
-        choices.append(questionary.Choice(title=display_name, value=relative_path))
-        
         try:
-            subdirs = sorted([p for p in current_path.iterdir() if p.is_dir() and p.name not in config.EXCLUDED_DIRS])
-            for subdir in subdirs:
-                scanner(subdir, depth + 1)
+            # Get a sorted list of valid subdirectories
+            subdirs = sorted([
+                p for p in current_path.iterdir()
+                if p.is_dir() and p.name not in config.EXCLUDED_DIRS
+            ])
+            
+            # Iterate through the subdirectories to build the tree display
+            for i, subdir in enumerate(subdirs):
+                is_last = (i == len(subdirs) - 1)
+                
+                # Use '└─' for the last item and '├─' for others
+                connector = "└─ " if is_last else "├─ "
+                display_name = f"{prefix}{connector}{subdir.name}"
+                
+                relative_path = subdir.relative_to(root_path)
+                choices.append(questionary.Choice(title=display_name, value=relative_path))
+                
+                # Prepare the prefix for the next level of recursion
+                # Use a blank prefix for children of the last item, and a pipe for others
+                child_prefix = prefix + ("    " if is_last else "│   ")
+                scanner(subdir, child_prefix, depth + 1)
+
         except PermissionError:
+            # Silently ignore directories that the user doesn't have permission to read
             pass
 
-    top_level_folders = sorted([p for p in root_path.iterdir() if p.is_dir() and p.name not in config.EXCLUDED_DIRS])
-    for folder in top_level_folders:
-        scanner(folder, 1)
+    # Start the recursive scan from the project's root directory
+    scanner(root_path, prefix="", depth=1)
         
+    # Add the special option to select files in the root folder itself
     root_option_name = f"root [{root_path.name}] (files in root folder only, excl. sub-folders)"
     choices.insert(0, questionary.Choice(title=root_option_name, value="ROOT_SENTINEL"))
     
@@ -49,15 +66,20 @@ def is_allowed_file(path: Path, exclude_large: bool) -> bool:
         return False
     if path.name.lower() in config.EXCLUDED_FILENAMES:
         return False
-    if path.suffix not in config.ALLOWED_EXTENSIONS:
+    if path.suffix.lower() not in config.ALLOWED_EXTENSIONS:
         return False
     if exclude_large and path.stat().st_size > config.MAX_FILE_SIZE_MB * 1024 * 1024:
         return False
     return True
 
 
-def extract_code_from_folder(folder: Path, exclude_large: bool) -> (str, int):
-    """Extracts code from a given folder, respecting EXCLUDED_DIRS at all depths."""
+def extract_code_from_folder(folder: Path, exclude_large: bool) -> tuple[str, int, int, int]:
+    """
+    Extracts code from a given folder, respecting EXCLUDED_DIRS at all depths.
+    
+    Returns:
+        A tuple containing the content string, file count, char count, and word count.
+    """
     content = f"# Folder: {folder.relative_to(Path.cwd())}\n\n"
     extracted_files = 0
     dirs_to_visit = [folder]
@@ -80,11 +102,21 @@ def extract_code_from_folder(folder: Path, exclude_large: bool) -> (str, int):
                     content += f"\n\n"
     if extracted_files > config.FILE_COUNT_WARNING_THRESHOLD:
         logging.warning(colored(f"> Caution: Large file count in '{folder.name}' ({extracted_files} files).", "yellow"))
-    return content, extracted_files
+    
+    # ADDED: Calculate character and word counts
+    char_count = len(content)
+    word_count = len(content.split())
+    
+    return content, extracted_files, char_count, word_count
 
 
-def extract_code_from_root(root_path: Path, exclude_large: bool) -> (str, int):
-    """Extracts code only from files present in the root directory."""
+def extract_code_from_root(root_path: Path, exclude_large: bool) -> tuple[str, int, int, int]:
+    """
+    Extracts code only from files present in the root directory.
+    
+    Returns:
+        A tuple containing the content string, file count, char count, and word count.
+    """
     content = f"# Root Files: {root_path.name}\n\n"
     extracted_files = 0
     for filepath in sorted(root_path.iterdir()):
@@ -97,7 +129,12 @@ def extract_code_from_root(root_path: Path, exclude_large: bool) -> (str, int):
             extracted_files += 1
     if extracted_files > config.FILE_COUNT_WARNING_THRESHOLD:
         logging.warning(colored(f"> Caution: Large file count in root ({extracted_files} files).", "yellow"))
-    return content, extracted_files
+    
+    # ADDED: Calculate character and word counts
+    char_count = len(content)
+    word_count = len(content.split())
+
+    return content, extracted_files, char_count, word_count
 
 
 def write_to_markdown_file(content: str, metadata: dict, root_path: Path, output_dir_name: str):
@@ -116,12 +153,15 @@ def write_to_markdown_file(content: str, metadata: dict, root_path: Path, output
     filename = f"{file_base_name}_{timestamp}.md"
     full_filepath = output_dir / filename
 
+    # CHANGED: Added char_count and word_count to the YAML header
     yaml_header = f"""---
 extraction_details:
   reference: {metadata['run_ref']}
   timestamp_utc: "{metadata['run_timestamp']}"
   source_folder: "{metadata['folder_name']}"
   file_count: {metadata['file_count']}
+  char_count: {metadata['char_count']}
+  word_count: {metadata['word_count']}
 tool_details:
   name: "Codebase Extractor"
   version: "{__version__}"

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0}/src/codebase_extractor/main_logic.py

@@ -35,7 +35,7 @@ class NumberValidator(Validator):
                 message="Please enter a valid number.",
                 cursor_position=len(document.text))
 
-def setup_logging(verbose: bool, log_file: str = None):
+def setup_logging(verbose: bool, log_file: Optional[str] = None):
     """Configures the logging system."""
     log_level = logging.DEBUG if verbose else logging.INFO
     log_format = logging.Formatter('%(message)s')
@@ -79,14 +79,14 @@ def main():
         # --- Startup Sequence ---
         if not is_fully_automated:
             ui.clear_screen()
-            ui.print_banner(no_instructions=args.no_instructions)
-            if not args.no_instructions:
+            # CHANGED: Pass the new 'instructions' flag to the banner function
+            ui.print_banner(show_instructions=args.instructions)
+            # CHANGED: Logic is now inverted to show instructions only when the flag is present
+            if args.instructions:
                 ui.show_instructions(output_dir_name)
-            else:
-                input(colored("\nPress Enter to begin...", "green"))
-                ui.clear_screen()
         else:
-            ui.print_banner(no_instructions=True)
+            # NOTE: For automated runs, the banner is always minimal. This is correct.
+            ui.print_banner(show_instructions=False)
         
         # --- Collect Settings (Interactively or from Args) ---
         select_style = Style([('qmark', 'fg:#FFA500'), ('pointer', 'fg:#FFA500'), ('highlighted', 'fg:black bg:#FFA500'), ('selected', 'fg:black bg:#FFA500')])
@@ -94,7 +94,7 @@ def main():
         exclude_large = args.exclude_large_files
         if not is_fully_automated:
             logging.info("=== Extraction Settings ===")
-            exclude_large_choice = questionary.select("[1/2] -- Exclude files larger than 1MB?", choices=["yes", "no"], style=select_style, instruction=" ").ask()
+            exclude_large_choice = questionary.select("[1/2] -- Exclude files larger than 1MB?", choices=["no", "yes"], style=select_style, instruction=" ").ask()
             if exclude_large_choice is None: raise KeyboardInterrupt
             exclude_large = exclude_large_choice == "yes"
             print()
@@ -148,13 +148,23 @@ def main():
         for folder_path in sorted(list(folders_to_process)):
             with Halo(text=f"Extracting {folder_path.relative_to(root_path)}...", spinner="dots"):
                 time.sleep(0.1)
-                folder_md, folder_count = file_handler.extract_code_from_folder(folder_path, exclude_large)
+                # CHANGED: Unpack the new char_count and word_count values
+                folder_md, folder_count, char_count, word_count = file_handler.extract_code_from_folder(folder_path, exclude_large)
             
             if folder_count > 0:
-                metadata = {"run_ref": run_ref, "run_timestamp": run_timestamp, "folder_name": str(folder_path.relative_to(root_path)), "file_count": folder_count}
+                # CHANGED: Add new metrics to the metadata dictionary
+                metadata = {
+                    "run_ref": run_ref, 
+                    "run_timestamp": run_timestamp, 
+                    "folder_name": str(folder_path.relative_to(root_path)), 
+                    "file_count": folder_count,
+                    "char_count": char_count,
+                    "word_count": word_count
+                }
                 if not args.dry_run:
                     file_handler.write_to_markdown_file(folder_md, metadata, root_path, output_dir_name)
                 logging.info(f"✅ Extracted {folder_count} file(s) from: {folder_path.relative_to(root_path)}")
+                logging.info(f"📜 {char_count:,} character(s), {word_count:,} word(s)")
                 if args.dry_run: logging.info(colored(" (Dry Run: No file written)", "yellow"))
                 total_files_extracted += folder_count
             else:
@@ -165,14 +175,24 @@ def main():
             root_display_name = f"root [{root_path.name}] (files in root folder only, excl. sub-folders)"
             with Halo(text=f"Extracting {root_display_name}...", spinner="dots"):
                 time.sleep(0.1)
-                root_md, root_count = file_handler.extract_code_from_root(root_path, exclude_large)
+                # CHANGED: Unpack the new char_count and word_count values
+                root_md, root_count, char_count, word_count = file_handler.extract_code_from_root(root_path, exclude_large)
             
             if root_count > 0:
-                metadata = {"run_ref": run_ref, "run_timestamp": run_timestamp, "folder_name": root_display_name, "file_count": root_count}
+                # CHANGED: Add new metrics to the metadata dictionary
+                metadata = {
+                    "run_ref": run_ref, 
+                    "run_timestamp": run_timestamp, 
+                    "folder_name": root_display_name, 
+                    "file_count": root_count,
+                    "char_count": char_count,
+                    "word_count": word_count
+                }
                 if not args.dry_run:
                     file_handler.write_to_markdown_file(root_md, metadata, root_path, output_dir_name)
                 total_files_extracted += root_count
                 logging.info(f"✅ Extracted {root_count} file(s) from the root directory")
+                logging.info(f"📜 {char_count:,} character(s), {word_count:,} word(s)")
                 if args.dry_run: logging.info(colored(" (Dry Run: No file written)", "yellow"))
             else:
                 logging.warning("‼️ No extractable files in the root directory")
@@ -196,4 +216,7 @@ def main():
         logging.error(colored(f"\n[!] An unexpected error occurred: {e}", "red"))
         import traceback
         traceback.print_exc()
-        sys.exit(1)
+        sys.exit(1)
+
+if __name__ == "__main__":
+    main()

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0}/src/codebase_extractor/ui.py

@@ -4,8 +4,6 @@ from . import config
 from . import __version__  
 from termcolor import colored
 
-# ... (LOGO_LARGE and LOGO_SMALL strings remain the same) ...
-
 LOGO_LARGE = """
  ██████╗ ██████╗ ██████╗ ███████╗██████╗  █████╗ ███████╗███████╗    ███████╗██╗  ██╗████████╗██████╗  █████╗  ██████╗████████╗ ██████╗ ██████╗ 
 ██╔════╝██╔═══██╗██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔════╝██╔════╝    ██╔════╝╚██╗██╔╝╚══██╔══╝██╔══██╗██╔══██╗██╔════╝╚══██╔══╝██╔═══██╗██╔══██╗
@@ -16,26 +14,16 @@ LOGO_LARGE = """
 """
 
 LOGO_SMALL = """
- ██████╗ ██████╗ ██████╗ ███████╗██████╗  █████╗ ███████╗███████╗          
-██╔════╝██╔═══██╗██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔════╝██╔════╝          
-██║     ██║   ██║██║  ██║█████╗  ██████╔╝███████║███████╗█████╗            
-██║     ██║   ██║██║  ██║██╔══╝  ██╔══██╗██╔══██║╚════██║██╔══╝            
-╚██████╗╚██████╔╝██████╔╝███████╗██████╔╝██║  ██║███████║███████╗          
- ╚═════╝ ╚═════╝ ╚═════╝ ╚══════╝╚═════╝ ╚═╝  ╚═╝╚══════╝╚══════╝          
-                                                                           
-███████╗██╗  ██╗████████╗██████╗  █████╗  ██████╗████████╗ ██████╗ ██████╗ 
-██╔════╝╚██╗██╔╝╚══██╔══╝██╔══██╗██╔══██╗██╔════╝╚══██╔══╝██╔═══██╗██╔══██╗
-█████╗   ╚███╔╝    ██║   ██████╔╝███████║██║        ██║   ██║   ██║██████╔╝
-██╔══╝   ██╔██╗    ██║   ██╔══██╗██╔══██║██║        ██║   ██║   ██║██╔══██╗
-███████╗██╔╝ ██╗   ██║   ██║  ██║██║  ██║╚██████╗   ██║   ╚██████╔╝██║  ██║
-╚══════╝╚═╝  ╚═╝   ╚═╝   ╚═╝  ╚═╝╚═╝  ╚═╝ ╚═════╝   ╚═╝    ╚═════╝ ╚═╝  ╚═╝
+  ░█▀▀░█▀█░█▀▄░█▀▀░█▀▄░█▀█░█▀▀░█▀▀░░░█▀▀░█░█░▀█▀░█▀▄░█▀█░█▀▀░▀█▀░█▀█░█▀▄
+  ░█░░░█░█░█░█░█▀▀░█▀▄░█▀█░▀▀█░█▀▀░░░█▀▀░▄▀▄░░█░░█▀▄░█▀█░█░░░░█░░█░█░█▀▄
+  ░▀▀▀░▀▀▀░▀▀░░▀▀▀░▀▀░░▀░▀░▀▀▀░▀▀▀░░░▀▀▀░▀░▀░░▀░░▀░▀░▀░▀░▀▀▀░░▀░░▀▀▀░▀░▀
 """
 
 def clear_screen():
     """Clears the terminal screen."""
     os.system('cls' if os.name == 'nt' else 'clear')
 
-def print_banner(no_instructions: bool = False):
+def print_banner(show_instructions: bool = False):
     """Prints a banner that adjusts to the terminal width."""
     try:
         width = shutil.get_terminal_size((80, 20)).columns
@@ -48,11 +36,10 @@ def print_banner(no_instructions: bool = False):
         print(LOGO_SMALL)
 
     # Use the imported __version__ variable instead of config.SCRIPT_VERSION
-    print(colored(f" Welcome to Code Extractor v{__version__} by Lukasz Lekowski ".center(width, "="), "white", "on_magenta"))
-    
-    if not no_instructions:
-        print("\nThis tool consolidates your project's code into structured Markdown files.")
-        print("It's ideal for providing context to AI models, archiving projects, or generating documentation.")
+    print(colored(f" Welcome to Codebase Extractor v{__version__} by Lukasz Lekowski ".center(width, "="), "white", "on_magenta"))
+    print("\nThis tool consolidates your project's codebase into structured Markdown files.")
+    print("It's ideal for providing context to AI models, archiving projects, or generating documentation.\n")
+
 
 def show_instructions(output_dir_name: str):
     """Clears screen and shows detailed instructions, pausing for user input."""
@@ -80,12 +67,13 @@ def show_instructions(output_dir_name: str):
     print("  - Selection Tree: You'll see a tree-like list of your project's folders. The script handles parent/child selections intelligently:")
     print("    - If you select a parent folder, all of its sub-folders are automatically included. You don't need to check them individually.")
     print("    - To get a file for *only* a sub-folder, select the sub-folder but *not* its parent.")
-    print("  - The 'root [...]' option specifically extracts *only* the files in your project's main directory.\n")
+    print("  - The 'root [...]' option specifically extracts *only* the files (not files in sub-folders) in your project's main directory.\n")
     
     print(colored("--- Output Details ---", "yellow"))
     print(f"All extracted content is saved into the '{output_dir_name}' directory. Each Markdown file generated will contain a YAML metadata header at the top with a unique reference ID, a timestamp, and more.\n")
     
-    tip = "TIP: Run this script with the --no-instructions or -ni flag to skip this guide."
+    # CHANGED: Updated the tip to reflect the new '--instructions' flag
+    tip = "TIP: To see this guide again, run the script with the --instructions flag."
     print(colored(tip, "black", "on_yellow"))
 
     input(colored("\nReady? Press Enter to begin...", "green"))
@@ -105,6 +93,4 @@ def print_footer():
     print("💡 Love this tool? Found a bug? Share your feedback on GitHub:")
     print(config.GITHUB_URL + "\n")
     print("🤝 Connect with the author on LinkedIn:")
-    print(config.LINKEDIN_URL + "\n")
-    print("☕ Enjoying this tool? You can support its development with a coffee!")
-    print("https://www.buymeacoffee.com/lukaszlekowski\n")
+    print(config.LINKEDIN_URL + "\n")

{codebase_extractor-1.1.0 → codebase_extractor-1.2.0/src/codebase_extractor.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codebase-extractor
-Version: 1.1.0
+Version: 1.2.0
 Summary: A CLI tool to extract project source code into structured Markdown files for LLM & AI context.
 Author: Lukasz Lekowski
 Project-URL: Homepage, https://github.com/lukaszlekowski/codebase-extractor
@@ -10,7 +10,7 @@ Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Classifier: Topic :: Software Development :: Documentation
 Classifier: Topic :: Utilities
-Requires-Python: >=3.9
+Requires-Python: >=3.14
 Description-Content-Type: text/markdown
 License-File: LICENCE
 Requires-Dist: questionary
@@ -75,12 +75,12 @@ The tool is highly configurable, allowing you to select specific folders, exclud
 ## ✨ Key Features
 
 - **Interactive & User-Friendly:** A guided, multi-step CLI experience that makes selecting options simple and clear.
+- **Quick Start by Default:** The tool starts without delay. Detailed instructions are available via an `--instructions` flag when you need a reminder.
 - **Smart Filtering:** Automatically excludes common dependency folders, build artifacts, version control directories, and IDE configuration files. The exact filters are configurable.
 - **Flexible Selection Modes:** Choose to extract the entire project with one command, or dive into a specific selection mode.
-- **🌳 Nested Folder Selection:** Interactively browse and select specific sub-folders from a tree-like view.
+- **🌳 Visual Tree Selection:** Interactively browse and select specific sub-folders from a clear, pipe-based tree structure.
 - **🔢 Configurable Scan Depth:** You decide how many levels deep the script should look for folders when building the selection tree.
-- **YAML Metadata:** Each generated Markdown file is prepended with a YAML front matter block containing useful metadata like a unique run ID, timestamp, and file count for easy tracking and parsing.
-- **🚀 Quick Start Mode:** Use the `--no-instructions` flag to skip the detailed intro guide on subsequent runs.
+- **Rich YAML Metadata:** Each generated Markdown file is prepended with a YAML front matter block containing useful metadata like a unique run ID, timestamp, file count, character count, and word count.
 - **Safe & Robust:** Features graceful exit handling (`Ctrl+C`) and provides clear feedback during the extraction process.
 
 ---
@@ -165,15 +165,15 @@ pipx install codebase-extractor
 Once installed, you can run the tool from any terminal window. Navigate to your project's root directory and run the command:
 
 ```bash
-code-extractor
+codebase-extractor
 ```
 
-The script will then guide you through the extraction process.
+The script will launch immediately and guide you through the extraction process.
 
-For repeat usage, you can skip the detailed introductory guide by using the `--no-instructions` or `-ni` flag:
+For a detailed guide on how the script works, you can use the `--instructions` flag:
 
 ```bash
-code-extractor --no-instructions
+codebase-extractor --instructions
 ```
 
 ### The Process
@@ -193,25 +193,25 @@ The tool will guide you through a series of prompts:
 
 ### Output Details
 
-All output files are saved in a `CODEBASE_EXTRACTS` directory within your project folder. Each generated Markdown file includes a YAML metadata header with a unique reference ID, timestamp, and file count for easy tracking and parsing.
+All output files are saved in a `CODEBASE_EXTRACTS` directory within your project folder. Each generated Markdown file includes a YAML metadata header with a unique reference ID, timestamp, file count, character count, and word count for easy tracking and parsing.
 
 ### ⚡ CLI Command Reference
 
 For non-interactive use and automation, you can control the script entirely with these arguments.
 
-| Argument                   | Description                                                                  | Default Value               |
-| :------------------------- | :--------------------------------------------------------------------------- | :-------------------------- |
-| `-ni`, `--no-instructions` | Run the script without printing the detailed instruction banner.             | `False`                     |
-| `--root <path>`            | The root directory of the project to extract.                                | The current directory       |
-| `--output-dir <name>`      | Custom name for the output directory.                                        | `CODEBASE_EXTRACTS`         |
-| `--dry-run`                | Simulate the extraction process without writing any files.                   | `False`                     |
-| `-v`, `--verbose`          | Enable verbose logging for debugging.                                        | `False`                     |
-| `--log-file <path>`        | Path to save the log file.                                                   | `None`                      |
-| `--exclude-large-files`    | Non-interactive: Exclude files larger than 1MB.                              | `False`                     |
-| `--mode <mode>`            | Non-interactive: Set the extraction mode. Choices: `everything`, `specific`. | `None` (Interactive prompt) |
-| `--depth <number>`         | Non-interactive: Set the folder scan depth for 'specific' mode.              | `3`                         |
-| `--select-folders <list>`  | Non-interactive: A space-separated list of folders/sub-folders to extract.   | `[]`                        |
-| `--select-root`            | Non-interactive: Include files from the root directory in the extraction.    | `False`                     |
+| Argument                  | Description                                                                  | Default Value               |
+| :------------------------ | :--------------------------------------------------------------------------- | :-------------------------- |
+| `--instructions`          | Show the detailed instruction guide on startup.                              | `False`                     |
+| `--root <path>`           | The root directory of the project to extract.                                | The current directory       |
+| `--output-dir <name>`     | Custom name for the output directory.                                        | `CODEBASE_EXTRACTS`         |
+| `--dry-run`               | Simulate the extraction process without writing any files.                   | `False`                     |
+| `-v`, `--verbose`         | Enable verbose logging for debugging.                                        | `False`                     |
+| `--log-file <path>`       | Path to save the log file.                                                   | `None`                      |
+| `--exclude-large-files`   | Non-interactive: Exclude files larger than 1MB.                              | `False`                     |
+| `--mode <mode>`           | Non-interactive: Set the extraction mode. Choices: `everything`, `specific`. | `None` (Interactive prompt) |
+| `--depth <number>`        | Non-interactive: Set the folder scan depth for 'specific' mode.              | `3`                         |
+| `--select-folders <list>` | Non-interactive: A space-separated list of folders/sub-folders to extract.   | `[]`                        |
+| `--select-root`           | Non-interactive: Include files from the root directory in the extraction.    | `False`                     |
 
 ---
 
@@ -224,7 +224,7 @@ Here are a few practical examples of how to use the tool from your command line.
   A common command for quick, automated runs.
 
   ```bash
-  code-extractor --no-instructions --mode everything
+  codebase-extractor --mode everything
   ```
 
 - #### Extract specific sub-folders non-interactively
@@ -232,7 +232,7 @@ Here are a few practical examples of how to use the tool from your command line.
   This command extracts only the `src/components` and `src/hooks` directories, plus any files in the root.
 
   ```bash
-  code-extractor --ni --mode specific --select-folders src/components src/hooks --select-root
+  codebase-extractor --mode specific --select-folders src/components src/hooks --select-root
   ```
 
 - #### Perform a safe dry run
@@ -240,13 +240,13 @@ Here are a few practical examples of how to use the tool from your command line.
   This will simulate a full extraction and print what it _would_ have done, without creating any files.
 
   ```bash
-  code-extractor --dry-run --mode everything
+  codebase-extractor --dry-run --mode everything
   ```
 
 - #### Run on a different project and save to a custom folder
   This targets a completely different directory and specifies a custom output folder name.
   ```bash
-  code-extractor --root /path/to/another/project --output-dir MyProject_Extraction
+  codebase-extractor --root /path/to/another/project --output-dir MyProject_Extraction
   ```
 
 ---
@@ -256,10 +256,11 @@ Here are a few practical examples of how to use the tool from your command line.
 The tool uses a set of rules to determine which files and folders to include in the extraction. Here are the default settings found in the `config.py` file.
 
 <details>
-  <summary><strong>Click to view Excluded Directories</strong></summary>
+<summary><strong>Click to view Excluded Directories</strong></summary>
   
   - `node_modules`, `vendor`, `__pycache__`, `dist`, `build`, `target`, `.next`
   - `.git`, `.svn`, `.hg`, `.vscode`, `.idea`, `venv`, `.venv`
+  - `.dart_tool`, `.gradle`, `Pods`, `DerivedData`
   
 </details>
 
@@ -273,17 +274,20 @@ The tool uses a set of rules to determine which files and folders to include in
 <details>
   <summary><strong>Click to view Allowed Filenames & Extensions</strong></summary>
   
-  The script will process any file with one of the following extensions. It also explicitly allows common configuration files that may not have an extension.
+The script will process any file with one of the following extensions. It also explicitly allows common configuration files that may not have an extension.
   
   **Allowed Filenames:**
-  - `dockerfile`, `.gitignore`, `.htaccess`, `makefile`
+  - `dockerfile`, `.gitignore`, `.htaccess`, `makefile`, `.dockerignore`, `.env.example`
+  - `podfile`, `gemfile`, `jenkinsfile`, `gradlew`
   
   **Allowed Extensions:**
-  - `.php`, `.html`, `.css`, `.js`, `.jsx`, `.ts`, `.tsx`, `.vue`, `.svelte`
-  - `.py`, `.rb`, `.java`, `.c`, `.cpp`, `.cs`, `.go`, `.rs`
-  - `.json`, `.xml`, `.yaml`, `.yml`, `.toml`, `.ini`, `.conf`
-  - `.md`, `.txt`, `.rst`, `.twig`, `.blade`, `.handlebars`, `.mustache`, `.ejs`
-  - `.sql`, `.graphql`, `.gql`, `.tf`
+  - **Web & General:** `.php`, `.html`, `.css`, `.js`, `.jsx`, `.ts`, `.tsx`, `.vue`, `.svelte`
+  - **Backend & Systems:** `.py`, `.rb`, `.java`, `.c`, `.cpp`, `.cs`, `.go`, `.rs`
+  - **Config & Data:** `.json`, `.xml`, `.yaml`, `.yml`, `.toml`, `.ini`, `.conf`
+  - **Docs & Templates:** `.md`, `.txt`, `.rst`, `.twig`, `.blade`, `.handlebars`, `.mustache`, `.ejs`
+  - **Database & IaC:** `.sql`, `.graphql`, `.gql`, `.tf`
+  - **Mobile (Flutter, Android, iOS):** `.dart`, `.arb`, `.gradle`, `.properties`, `.plist`, `.xcconfig`
+  - **Scripts:** `.sh`, `.bat`
   
 </details>
 
@@ -291,7 +295,7 @@ The tool uses a set of rules to determine which files and folders to include in
 
 ## 🤔 Troubleshooting
 
-- **Problem:** After installation, I run `code-extractor` and my terminal says `command not found`.
+- **Problem:** After installation, I run `codebase-extractor` and my terminal says `command not found`.
 - **Solution:** This is usually a `PATH` issue. It means your system's shell doesn't know where to find the installed script. The `pip install --user` command sometimes requires you to add a local scripts directory to your `PATH`. Please refer to your operating system's documentation for instructions on how to modify your `PATH` environment variable.
 
 - **Problem:** The tool ran, but a specific folder or file I expected to see is missing from the output.

codebase_extractor-1.2.0/src/codebase_extractor.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+codebase-extractor = codebase_extractor.main_logic:main

codebase_extractor-1.1.0/src/codebase_extractor/__init__.py

@@ -1 +0,0 @@
-__version__ = "1.1.0"

codebase_extractor-1.1.0/src/codebase_extractor.egg-info/entry_points.txt

@@ -1,2 +0,0 @@
-[console_scripts]
-code-extractor = codebase_extractor.main_logic:main