Add more files from chat:

https://claude.ai/chat/8fc53364-a63b-41b9-95fc-4c04e1c46058

Author: vgrichina

docs/apply-md.md

@@ -0,0 +1,96 @@
+# `apply-md` - Markdown Code Applier
+
+## Overview
+
+The `apply-md` tool extracts code blocks from markdown (typically LLM responses) and applies them to your filesystem.
+
+## Usage
+
+```bash
+cat llm_response.md | ./apply-md --dry-run --verbose
+```
+
+## Arguments
+
+| Argument | Description | Default |
+|----------|-------------|---------|
+| `--dry-run` | Preview changes without applying them | False |
+| `--create-missing` | Create files that don't exist | False |
+| `--backup` | Create backup files before applying changes | False |
+| `--backup-dir=<dir>` | Directory for backups | "./.backups" |
+| `--file-marker=<regex>` | Regex to identify target files from markdown | "```[a-z]+ (.+)" |
+| `--skip-unchanged` | Skip files with no changes | False |
+| `--verbose` | Show detailed output about changes | False |
+| `--confirm` | Prompt for confirmation before applying each change | False |
+| `--only-files=<pattern>` | Only apply changes to files matching pattern | None |
+| `--ignore-files=<pattern>` | Ignore changes for files matching pattern | None |
+
+## How It Works
+
+1. The tool reads markdown content from stdin
+2. It looks for code blocks that specify a filename (e.g., ```javascript src/utils.js)
+3. It extracts the code from these blocks
+4. It applies the code to the corresponding files in your filesystem
+
+## Examples
+
+### Basic Usage
+
+Apply changes directly from an LLM response:
+
+```bash
+cat llm_response.md | ./apply-md
+```
+
+### Dry Run
+
+Preview changes without applying them:
+
+```bash
+cat llm_response.md | ./apply-md --dry-run --verbose
+```
+
+### With Backups
+
+Make backups before applying changes:
+
+```bash
+cat llm_response.md | ./apply-md --backup
+```
+
+### Creating New Files
+
+Allow creating files that don't exist:
+
+```bash
+cat llm_response.md | ./apply-md --create-missing
+```
+
+### Selective Application
+
+Only apply changes to specific files:
+
+```bash
+cat llm_response.md | ./apply-md --only-files="*.js"
+```
+
+## Expected Markdown Format
+
+The script expects code blocks in this format:
+
+````
+```javascript src/utils.js
+function add(a, b) {
+  return a + b;
+}
+```
+````
+
+The language specification is optional, but the filename is required.
+
+## Tips
+
+- Always use `--dry-run` first to preview changes
+- Consider using `--backup` for important changes
+- Use `--verbose` to see details about what's changing
+- For complex changes, use `--confirm` to review each change individually

docs/context.md

@@ -0,0 +1,76 @@
+# `context` - Code Context Generator
+
+## Overview
+
+The `context` tool extracts relevant code and context from your codebase to send to an LLM (Large Language Model).
+
+## Usage
+
+```bash
+./context --files="src/components/*.js" --exclude="*.test.js" --max-size=300KB --format=md > context.txt
+```
+
+## Arguments
+
+| Argument | Description | Default |
+|----------|-------------|---------|
+| `--files=<pattern>` | File pattern to include (e.g., "src/*.js") | Required |
+| `--exclude=<pattern>` | File pattern to exclude (e.g., "node_modules/**") | None |
+| `--max-size=<size>` | Maximum context size in KB/MB (e.g., "500KB") | "500KB" |
+| `--include-deps` | Include dependent files based on imports/requires | False |
+| `--depth=<num>` | Dependency traversal depth | 1 |
+| `--include-git` | Include git information (recent commits, authors) | False |
+| `--git-depth=<num>` | Number of recent commits to include | 3 |
+| `--format=<format>` | Output format (md, json, text) | "md" |
+| `--summary` | Include short summary of each file | False |
+| `--show-file-sizes` | Include file sizes in output | False |
+| `--truncate-large=<size>` | Truncate files larger than specified size (e.g., "50KB") | None |
+
+## Examples
+
+### Basic Usage
+
+Extract all JS files in the src directory:
+
+```bash
+./context --files="src/**/*.js" > code_context.md
+```
+
+### With Dependencies
+
+Include imported/required files (1 level deep):
+
+```bash
+./context --files="src/components/Button.js" --include-deps > button_context.md
+```
+
+### Include Git Information
+
+Generate context with git history:
+
+```bash
+./context --files="src/utils/*.js" --include-git --git-depth=5 > utils_context.md
+```
+
+### JSON Output
+
+Get context in JSON format for programmatic usage:
+
+```bash
+./context --files="*.py" --format=json > context.json
+```
+
+## Customization
+
+The script is designed to be simple and easy to modify. You can:
+
+1. Add support for more languages in the dependency resolution
+2. Modify the output format for your specific needs
+3. Add additional metadata to the context generation
+
+## Tips
+
+- When working with LLMs, try to keep the context focused and relevant
+- Use `--exclude` to filter out test files, build artifacts, etc.
+- The `--summary` flag can help provide high-level context about each file
+- If you hit token limits, use `--truncate-large` to limit file sizes

docs/git-context.md

@@ -0,0 +1,95 @@
+# `git-context` - Git Context Generator
+
+## Overview
+
+The `git-context` tool generates git-related context specifically to help LLMs create meaningful commit messages.
+
+## Usage
+
+```bash
+./git-context --diff --recent-commits=2 --prompt --conventional > commit_context.txt
+```
+
+## Arguments
+
+| Argument | Description | Default |
+|----------|-------------|---------|
+| `--diff` | Show uncommitted changes | True |
+| `--no-diff` | Don't show uncommitted changes | False |
+| `--staged` | Show only staged changes | False |
+| `--unstaged` | Show only unstaged changes | False |
+| `--recent-commits=<num>` | Show most recent N commits for context | 3 |
+| `--files=<pattern>` | Include only files matching pattern | None |
+| `--exclude=<pattern>` | Exclude files matching pattern | None |
+| `--format=<format>` | Output format (md, json, text) | "md" |
+| `--prompt` | Include commit message generation prompt | False |
+| `--conventional` | Add conventional commit format guidance | False |
+| `--project-context` | Include project name and description for context | False |
+| `--branch-info` | Include current branch and related info | False |
+
+## Output
+
+The tool outputs git context information, which typically includes:
+
+1. Git diff of uncommitted/staged changes
+2. Information about files changed (stats)
+3. Recent commit messages for style reference
+4. Optional prompt to guide the LLM in generating a good commit message
+
+## Examples
+
+### Basic Usage
+
+Generate context for a commit message:
+
+```bash
+./git-context > commit_context.txt
+```
+
+### Conventional Commits
+
+Include guidance for conventional commit format:
+
+```bash
+./git-context --prompt --conventional > commit_context.txt
+```
+
+### With Project Context
+
+Include project information for better context:
+
+```bash
+./git-context --project-context --branch-info > commit_context.txt
+```
+
+### Staged Changes Only
+
+Only include changes that have been staged:
+
+```bash
+./git-context --staged --prompt > commit_context.txt
+```
+
+### JSON Output
+
+Generate context in JSON format:
+
+```bash
+./git-context --format=json > commit_context.json
+```
+
+## Customization
+
+The commit message prompt template is stored in `prompts/commit_prompt.txt` and can be customized to your project's needs.
+
+If the `--conventional` flag is used, the tool will also include guidance from `prompts/conventional_commit.txt`.
+
+## Workflow Integration
+
+Typical workflow:
+
+1. Make changes to your code
+2. Stage changes with `git add`
+3. Run `./git-context --staged --prompt > commit_context.txt`
+4. Send commit_context.txt to an LLM to generate a commit message
+5. Use the generated message with `git commit -m "generated message"`