Tools Repository

A centralized collection of utility scripts and tools for consistent development environments across machines.

Platform Support

macOS (Intel and Apple Silicon)
Linux (Ubuntu, Debian, Fedora, Arch, and other major distributions)
Windows (via WSL or Git Bash)

This repository serves as a single source of truth for commonly used tools, scripts, and utilities that enhance productivity across different development environments. It provides a quick and reliable way to set up these tools on any supported platform with automatic installation of required dependencies.

Quick Setup

git clone <repository-url> ~/github/tools
cd ~/github/tools
./setup.sh
source ~/.zshrc

What It Does

Centralized Tool Management: Keep all your custom scripts and tools in one version-controlled location
Automatic Tool Installation: Installs required tools (Rust, code2prompt, etc.) automatically
Cross-Platform Support: Works seamlessly on Linux, macOS, and Windows (WSL/Git Bash)
Instant Availability: Automatically adds tools to your PATH for immediate use
Idempotent Setup: Safe to run the setup script multiple times without side effects
Portable Configuration: Easy to clone and set up on new machines or environments

Repository Structure

tools/
├── setup.sh           # Main setup script - PATH, permissions, and tool installation
├── scripts/           # Executable tools and utilities (SOURCE OF TRUTH)
│   └── sync-to-dist.sh # Syncs all source files to src/jk_tools/ for packaging
├── install/           # Tool installation scripts (SOURCE OF TRUTH)
│   ├── rust.sh        # Installs Rust and Cargo via rustup
│   ├── code2prompt.sh # Installs code2prompt via cargo
│   └── agents.sh      # Syncs to dist + installs commands to Claude/OpenCode/Codex CLIs
├── agents/            # AI agent assets (SOURCE OF TRUTH)
│   ├── commands/      # Markdown command definitions (edit here)
│   ├── mcp/           # Canonical MCP server definitions (edit here)
│   └── settings.local.json # Settings for agent commands (edit here)
├── src/jk_tools/      # Distribution package (AUTO-SYNCED - DO NOT EDIT)
│   ├── agents/        # Mirrored from agents/ (auto-synced)
│   ├── scripts/       # Mirrored from scripts/ (auto-synced)
│   ├── install/       # Mirrored from install/ (auto-synced)
│   ├── setup_manager.py # Mirrored from root (auto-synced)
│   ├── __init__.py    # Package-only file
│   └── cli.py         # Package-only entry point
├── scratch/           # Temporary workspace (gitignored)
├── AGENTS.md          # This file - documentation
└── LICENSE            # Repository license

Tool Installation

The setup script automatically checks for and installs required tools. Each tool has its own installation script in the

install/

directory.

Currently Automated Tools

Rust & Cargo: The Rust programming language and package manager
code2prompt: CLI tool to convert codebases into LLM prompts
Agent Commands: Custom commands for Claude, OpenCode, and Codex AI assistants
Agent MCP Config: Shared Serena MCP server config deployed to Codex CLI, Claude CLI, OpenCode CLI, and VS Code (global + project files)

VS Code MCP Configuration

Global config:

~/Library/Application Support/Code/User/mcp.json

on macOS,

~/.config/Code/User/mcp.json

on Linux

Project config:
```
./.vscode/mcp.json
```
(auto-generated by the installer)
Remote environments still require updating the remote user config via VS Code's "MCP: Open Remote User Configuration" command

Source/Distribution Paradigm

IMPORTANT: This repository uses a source/distribution model for packaging.

Source of Truth (Edit These)

```
agents/
```
- Agent commands, MCP configs, settings
```
scripts/
```
- Utility scripts
```
install/
```
- Installation scripts
```
setup_manager.py
```
- Setup manager
```
.vscode/
```
- VS Code planning commands

Distribution Copy (Never Edit)

```
src/jk_tools/
```
- Auto-synced mirror for Python package distribution
This directory is automatically synchronized by
```
./setup.sh
```
DO NOT edit files in
```
src/jk_tools/
```
- they will be overwritten

How Syncing Works

When you run

./setup.sh

, it:

Syncs source → distribution using
```
scripts/sync-to-dist.sh
```
Copies all files from root directories to
```
src/jk_tools/
```
Then installs tools to user directories (~/.claude/commands, etc.)

No manual sync needed! Just edit the source files and run

./setup.sh

What Gets Synced

✅ Automatically synced:

agents/commands/*.md

→

src/jk_tools/agents/commands/

```
agents/mcp/
```
→
```
src/jk_tools/agents/mcp/
```

agents/settings.local.json

→

src/jk_tools/agents/

```
scripts/
```
→
```
src/jk_tools/scripts/
```
```
install/
```
→
```
src/jk_tools/install/
```

setup_manager.py

→

src/jk_tools/setup_manager.py

```
.vscode/plan-*.md
```
and other planning commands →
```
src/jk_tools/.vscode/
```

❌ Not synced (package-only):

```
src/jk_tools/__init__.py
```
```
src/jk_tools/cli.py
```

❌ Not synced (project-specific):

```
.vscode/settings.json
```
```
.vscode/mcp.json
```

Adding New Agent Commands

To add a new agent command:

Create the command file in

agents/commands/

# Create new command
nano agents/commands/my-new-command.md

Run setup to sync and install:
```
./setup.sh
```

Command is now available in:

```
~/.claude/commands/my-new-command.md
```

~/.config/opencode/command/my-new-command.md

```
~/.codex/prompts/my-new-command.md
```

~/.config/github-copilot/prompts/my-new-command.prompt.md

src/jk_tools/agents/commands/my-new-command.md

(for distribution)

Installing Commands Locally (Project-Specific)

By default, commands are installed globally (user home directory). You can also install commands locally to a project directory for version control and team sharing:

Global Installation (Default)

# Installs to ~/.claude/commands, ~/.config/opencode/command, etc.
uvx jk-tools
./setup.sh

Local Installation (Project-Specific)

# Install commands locally to current directory
uvx jk-tools --commands-local claude,opencode,ghcp

# Install to specific directory
uvx jk-tools --commands-local claude --local-dir ~/my-project

Supported Local Paths

CLI Tool	Local Directory	Auto-Discovery	Status
Claude Code	`.claude/commands/`	✅ Yes	✅ Fully supported
OpenCode	`.opencode/command/`	✅ Yes	✅ Fully supported
GitHub Copilot	`.github/prompts/*.prompt.md`	⚠️ Manual attach	✅ Supported
Codex	N/A	❌ No	❌ Not supported

Local Installation Behavior

What gets installed:

✅ Command/prompt files ONLY
❌ NO MCP server configuration
❌ NO global setup
❌ NO other tools installation

Examples:

# Install from local repository (for development)
uvx jk-tools-setup --commands-local claude

# Install from GitHub (for production use)
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local claude

# Install GitHub Copilot commands from GitHub
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local ghcp

# Install to specific directory
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local claude --local-dir ~/my-project

# Install multiple CLIs at once
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local claude,ghcp,opencode

# Force reinstall to get latest version
uvx --force-reinstall --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local ghcp

# Result (Claude example):
# ./
# └── .claude/
#     └── commands/
#         ├── plan-0-constitution.md
#         ├── plan-1-specify.md
#         ├── tad.md
#         └── ... (14 command files)

GitHub Copilot Notes

Files are renamed with
```
.prompt.md
```
extension (e.g.,
```
tad.md
```
→
```
tad.prompt.md
```
)
Use the paperclip icon in your IDE to attach prompts
Alternatively, create
```
.github/copilot-instructions.md
```
for auto-loaded instructions

Codex Limitation

Codex does not currently support project-local commands (requested feature: GitHub issue #4734).

Workarounds:

Use global commands only:
```
~/.codex/prompts/
```
Set per-project:
```
CODEX_HOME=$(pwd)/.codex/
```
Use third-party tool: cx-prompts

Version Control

Local commands can be committed to git for team sharing:

# Add local commands to git
git add .claude/commands/
git add .opencode/command/
git add .github/prompts/

git commit -m "Add local AI CLI commands"
git push

Team members will automatically have access to project-specific commands after cloning.

Adding New Tools

To add a new tool to the repository:

For scripts/utilities: Place in
```
scripts/
```
directory
For tools requiring installation: Create an install script in
```
install/
```
directory
- Name it
```
install/<toolname>.sh
```
- Follow the pattern of existing install scripts
- Check if installed → Install if needed → Verify installation
Run
```
./setup.sh
```
to apply changes (syncs and installs)
Commit and push to share across your machines

Tool Development Guidelines

When creating new tools, follow these conventions:

Help System:
- Must support
```
--help
```
  flag for detailed documentation
- Should show help when called with no parameters (if safe to do so)
- Include: NAME, SYNOPSIS, DESCRIPTION, PARAMETERS, OPTIONS, EXAMPLES
- Format for both human and AI readability
Naming:
- Use descriptive names with dashes (e.g.,
```
analyze-dependencies.sh
```
  )
- Aliases will be auto-generated with
```
jk-
```
  prefix
Documentation:
- Include purpose and use cases
- Provide real-world examples
- List dependencies and requirements
- Specify expected output format
Integration:
- Make tools composable with Unix pipes
- Use exit codes appropriately (0 for success, non-zero for errors)
- Support common flags like
```
--help
```
  ,
```
--version
```
  ,
```
--verbose
```

Benefits

Consistency: Same tools available on all your development machines
Version Control: Track changes and improvements to your tools over time
Quick Onboarding: Set up a new machine with all your tools in seconds
No Manual PATH Management: Automatic PATH configuration for all tools
Clean Separation: Keeps custom tools separate from system utilities

Usage

After setup, any script in the

scripts/

directory can be called directly from anywhere in your terminal without specifying the full path.

Discovering Available Tools

To see all available tools and their descriptions:

jk-tools        # List all tools with descriptions
jk-jt           # Short alias for jk-tools
jk-tools -v     # Verbose mode with full help text

Getting Help

All tools follow a consistent help convention:

<tool-name> --help    # Get detailed help for any tool
jk-gcm --help         # Example: help for generate-codebase-md

Tool Aliases

Tools with dashes in their names automatically get

jk-

prefixed aliases:

```
generate-codebase-md.sh
```
→
```
jk-gcm
```
```
jk-tools.sh
```
→
```
jk-jt
```
Future tools follow the same pattern

For AI Assistants / LLMs

When working with this repository, AI assistants should:

Discover available tools: Run
```
jk-tools
```
to see all available utilities
Understand tool purpose: Each tool has comprehensive help via
```
--help
```
Use aliases: Prefer short aliases (e.g.,
```
jk-gcm
```
) for efficiency
Check requirements: Tools list their dependencies in help text
Use scratch directory: Output temporary files to
```
./scratch/
```
to keep repo clean
Git commands - READ ONLY: You may use any git command to read repository state (e.g.,
```
git status
```
,
```
git diff
```
,
```
git log
```
,
```
git show
```
), but NEVER modify git state (no
```
git add
```
,
```
git commit
```
,
```
git push
```
,
```
git checkout
```
, etc.) unless explicitly requested by the user

Example workflow for an AI assistant:

# 1. Discover what tools are available
jk-tools

# 2. Get detailed help for a specific tool
jk-gcm --help

# 3. Use the tool with appropriate parameters
jk-gcm ./scratch/analysis ./src

# 4. Process the generated markdown
cat ./scratch/analysis/codebase.md

Maintenance

Daily Workflow

Edit source files: Only edit files in root directories (agents/, scripts/, install/)
Never edit
```
src/jk_tools/
```
- it's auto-synced
Run setup:
```
./setup.sh
```
syncs and installs everything

Syncing

Automatic:
```
./setup.sh
```
syncs source → distribution automatically
Manual sync only:
```
./scripts/sync-to-dist.sh
```
(if needed without install)
No manual copying needed: Everything is handled automatically

Version Control

Pull latest changes:
```
git pull
```
Add new tools: Copy to
```
scripts/
```
and run
```
./setup.sh
```
Update existing tools: Edit in place and commit changes
Share across machines: Push to remote and pull on other machines
Commit both: Source files AND synced
```
src/jk_tools/
```
files

Scratch Directory (Ephemeral Workspace)

Use a top-level

scratch/

directory in this repository for temporary experiments, throwaway scripts, notes, or generated files you do not want tracked by Git.

Why

Keeps the repo clean of WIP and exploratory artifacts
Avoids accidental commits of large or sensitive temporary files
Provides an easy, predictable location for ad-hoc work

Usage

mkdir -p scratch
cd scratch
# Create or copy experimental files here

You can freely create, modify, and delete anything inside

scratch/

without impacting version control. The path is ignored via

.gitignore

Guidelines

Never store the only copy of important work here—it's untracked
Safe to wipe/recreate at any time
Use subfolders if juggling multiple experiments
If something becomes valuable, move it into a tracked location (e.g.
```
scripts/
```
) before committing

Automation Tip

Add helpers or prototypes here first; once stable, promote them into

scripts/

and run

./setup.sh

Tools Repository

A centralized collection of utility scripts and tools for consistent development environments across machines.

Platform Support

macOS (Intel and Apple Silicon)
Linux (Ubuntu, Debian, Fedora, Arch, and other major distributions)
Windows (via WSL or Git Bash)

Purpose

Quick Setup

git clone <repository-url> ~/github/tools
cd ~/github/tools
./setup.sh
source ~/.zshrc

What It Does

Centralized Tool Management: Keep all your custom scripts and tools in one version-controlled location
Automatic Tool Installation: Installs required tools (Rust, code2prompt, etc.) automatically
Cross-Platform Support: Works seamlessly on Linux, macOS, and Windows (WSL/Git Bash)
Instant Availability: Automatically adds tools to your PATH for immediate use
Idempotent Setup: Safe to run the setup script multiple times without side effects
Portable Configuration: Easy to clone and set up on new machines or environments

Repository Structure

tools/
├── setup.sh           # Main setup script - PATH, permissions, and tool installation
├── scripts/           # Executable tools and utilities (SOURCE OF TRUTH)
│   └── sync-to-dist.sh # Syncs all source files to src/jk_tools/ for packaging
├── install/           # Tool installation scripts (SOURCE OF TRUTH)
│   ├── rust.sh        # Installs Rust and Cargo via rustup
│   ├── code2prompt.sh # Installs code2prompt via cargo
│   └── agents.sh      # Syncs to dist + installs commands to Claude/OpenCode/Codex CLIs
├── agents/            # AI agent assets (SOURCE OF TRUTH)
│   ├── commands/      # Markdown command definitions (edit here)
│   ├── mcp/           # Canonical MCP server definitions (edit here)
│   └── settings.local.json # Settings for agent commands (edit here)
├── src/jk_tools/      # Distribution package (AUTO-SYNCED - DO NOT EDIT)
│   ├── agents/        # Mirrored from agents/ (auto-synced)
│   ├── scripts/       # Mirrored from scripts/ (auto-synced)
│   ├── install/       # Mirrored from install/ (auto-synced)
│   ├── setup_manager.py # Mirrored from root (auto-synced)
│   ├── __init__.py    # Package-only file
│   └── cli.py         # Package-only entry point
├── scratch/           # Temporary workspace (gitignored)
├── AGENTS.md          # This file - documentation
└── LICENSE            # Repository license

Tool Installation

The setup script automatically checks for and installs required tools. Each tool has its own installation script in the

install/

directory.

Currently Automated Tools

Rust & Cargo: The Rust programming language and package manager
code2prompt: CLI tool to convert codebases into LLM prompts
Agent Commands: Custom commands for Claude, OpenCode, and Codex AI assistants
Agent MCP Config: Shared Serena MCP server config deployed to Codex CLI, Claude CLI, OpenCode CLI, and VS Code (global + project files)

VS Code MCP Configuration

Global config:

~/Library/Application Support/Code/User/mcp.json

on macOS,

~/.config/Code/User/mcp.json

on Linux

Project config:
```
./.vscode/mcp.json
```
(auto-generated by the installer)
Remote environments still require updating the remote user config via VS Code's "MCP: Open Remote User Configuration" command

Source/Distribution Paradigm

IMPORTANT: This repository uses a source/distribution model for packaging.

Source of Truth (Edit These)

```
agents/
```
- Agent commands, MCP configs, settings
```
scripts/
```
- Utility scripts
```
install/
```
- Installation scripts
```
setup_manager.py
```
- Setup manager
```
.vscode/
```
- VS Code planning commands

Distribution Copy (Never Edit)

```
src/jk_tools/
```
- Auto-synced mirror for Python package distribution
This directory is automatically synchronized by
```
./setup.sh
```
DO NOT edit files in
```
src/jk_tools/
```
- they will be overwritten

How Syncing Works

When you run

./setup.sh

, it:

Syncs source → distribution using
```
scripts/sync-to-dist.sh
```
Copies all files from root directories to
```
src/jk_tools/
```
Then installs tools to user directories (~/.claude/commands, etc.)

No manual sync needed! Just edit the source files and run

./setup.sh

What Gets Synced

✅ Automatically synced:

agents/commands/*.md

→

src/jk_tools/agents/commands/

```
agents/mcp/
```
→
```
src/jk_tools/agents/mcp/
```

agents/settings.local.json

→

src/jk_tools/agents/

```
scripts/
```
→
```
src/jk_tools/scripts/
```
```
install/
```
→
```
src/jk_tools/install/
```

setup_manager.py

→

src/jk_tools/setup_manager.py

```
.vscode/plan-*.md
```
and other planning commands →
```
src/jk_tools/.vscode/
```

❌ Not synced (package-only):

```
src/jk_tools/__init__.py
```
```
src/jk_tools/cli.py
```

❌ Not synced (project-specific):

```
.vscode/settings.json
```
```
.vscode/mcp.json
```

Adding New Agent Commands

To add a new agent command:

Create the command file in

agents/commands/

# Create new command
nano agents/commands/my-new-command.md

Run setup to sync and install:
```
./setup.sh
```

Command is now available in:

```
~/.claude/commands/my-new-command.md
```

~/.config/opencode/command/my-new-command.md

```
~/.codex/prompts/my-new-command.md
```

~/.config/github-copilot/prompts/my-new-command.prompt.md

src/jk_tools/agents/commands/my-new-command.md

(for distribution)

Installing Commands Locally (Project-Specific)

By default, commands are installed globally (user home directory). You can also install commands locally to a project directory for version control and team sharing:

Global Installation (Default)

# Installs to ~/.claude/commands, ~/.config/opencode/command, etc.
uvx jk-tools
./setup.sh

Local Installation (Project-Specific)

# Install commands locally to current directory
uvx jk-tools --commands-local claude,opencode,ghcp

# Install to specific directory
uvx jk-tools --commands-local claude --local-dir ~/my-project

Supported Local Paths

CLI Tool	Local Directory	Auto-Discovery	Status
Claude Code	`.claude/commands/`	✅ Yes	✅ Fully supported
OpenCode	`.opencode/command/`	✅ Yes	✅ Fully supported
GitHub Copilot	`.github/prompts/*.prompt.md`	⚠️ Manual attach	✅ Supported
Codex	N/A	❌ No	❌ Not supported

Local Installation Behavior

What gets installed:

✅ Command/prompt files ONLY
❌ NO MCP server configuration
❌ NO global setup
❌ NO other tools installation

Examples:

# Install from local repository (for development)
uvx jk-tools-setup --commands-local claude

# Install from GitHub (for production use)
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local claude

# Install GitHub Copilot commands from GitHub
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local ghcp

# Install to specific directory
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local claude --local-dir ~/my-project

# Install multiple CLIs at once
uvx --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local claude,ghcp,opencode

# Force reinstall to get latest version
uvx --force-reinstall --from git+https://github.com/jakkaj/tools jk-tools-setup --commands-local ghcp

# Result (Claude example):
# ./
# └── .claude/
#     └── commands/
#         ├── plan-0-constitution.md
#         ├── plan-1-specify.md
#         ├── tad.md
#         └── ... (14 command files)

GitHub Copilot Notes

Files are renamed with
```
.prompt.md
```
extension (e.g.,
```
tad.md
```
→
```
tad.prompt.md
```
)
Use the paperclip icon in your IDE to attach prompts
Alternatively, create
```
.github/copilot-instructions.md
```
for auto-loaded instructions

Codex Limitation

Codex does not currently support project-local commands (requested feature: GitHub issue #4734).

Workarounds:

Use global commands only:
```
~/.codex/prompts/
```
Set per-project:
```
CODEX_HOME=$(pwd)/.codex/
```
Use third-party tool: cx-prompts

Version Control

Local commands can be committed to git for team sharing:

# Add local commands to git
git add .claude/commands/
git add .opencode/command/
git add .github/prompts/

git commit -m "Add local AI CLI commands"
git push

Team members will automatically have access to project-specific commands after cloning.

Adding New Tools

To add a new tool to the repository:

For scripts/utilities: Place in
```
scripts/
```
directory
For tools requiring installation: Create an install script in
```
install/
```
directory
- Name it
```
install/<toolname>.sh
```
- Follow the pattern of existing install scripts
- Check if installed → Install if needed → Verify installation
Run
```
./setup.sh
```
to apply changes (syncs and installs)
Commit and push to share across your machines

Tool Development Guidelines

When creating new tools, follow these conventions:

Help System:
- Must support
```
--help
```
  flag for detailed documentation
- Should show help when called with no parameters (if safe to do so)
- Include: NAME, SYNOPSIS, DESCRIPTION, PARAMETERS, OPTIONS, EXAMPLES
- Format for both human and AI readability
Naming:
- Use descriptive names with dashes (e.g.,
```
analyze-dependencies.sh
```
  )
- Aliases will be auto-generated with
```
jk-
```
  prefix
Documentation:
- Include purpose and use cases
- Provide real-world examples
- List dependencies and requirements
- Specify expected output format
Integration:
- Make tools composable with Unix pipes
- Use exit codes appropriately (0 for success, non-zero for errors)
- Support common flags like
```
--help
```
  ,
```
--version
```
  ,
```
--verbose
```

Benefits

Consistency: Same tools available on all your development machines
Version Control: Track changes and improvements to your tools over time
Quick Onboarding: Set up a new machine with all your tools in seconds
No Manual PATH Management: Automatic PATH configuration for all tools
Clean Separation: Keeps custom tools separate from system utilities

Usage

After setup, any script in the

scripts/

directory can be called directly from anywhere in your terminal without specifying the full path.

Discovering Available Tools

To see all available tools and their descriptions:

jk-tools        # List all tools with descriptions
jk-jt           # Short alias for jk-tools
jk-tools -v     # Verbose mode with full help text

Getting Help

All tools follow a consistent help convention:

<tool-name> --help    # Get detailed help for any tool
jk-gcm --help         # Example: help for generate-codebase-md

Tool Aliases

Tools with dashes in their names automatically get

jk-

prefixed aliases:

```
generate-codebase-md.sh
```
→
```
jk-gcm
```
```
jk-tools.sh
```
→
```
jk-jt
```
Future tools follow the same pattern

For AI Assistants / LLMs

When working with this repository, AI assistants should:

Discover available tools: Run
```
jk-tools
```
to see all available utilities
Understand tool purpose: Each tool has comprehensive help via
```
--help
```
Use aliases: Prefer short aliases (e.g.,
```
jk-gcm
```
) for efficiency
Check requirements: Tools list their dependencies in help text
Use scratch directory: Output temporary files to
```
./scratch/
```
to keep repo clean
Git commands - READ ONLY: You may use any git command to read repository state (e.g.,
```
git status
```
,
```
git diff
```
,
```
git log
```
,
```
git show
```
), but NEVER modify git state (no
```
git add
```
,
```
git commit
```
,
```
git push
```
,
```
git checkout
```
, etc.) unless explicitly requested by the user

Example workflow for an AI assistant:

# 1. Discover what tools are available
jk-tools

# 2. Get detailed help for a specific tool
jk-gcm --help

# 3. Use the tool with appropriate parameters
jk-gcm ./scratch/analysis ./src

# 4. Process the generated markdown
cat ./scratch/analysis/codebase.md

Maintenance

Daily Workflow

Edit source files: Only edit files in root directories (agents/, scripts/, install/)
Never edit
```
src/jk_tools/
```
- it's auto-synced
Run setup:
```
./setup.sh
```
syncs and installs everything

Syncing

Automatic:
```
./setup.sh
```
syncs source → distribution automatically
Manual sync only:
```
./scripts/sync-to-dist.sh
```
(if needed without install)
No manual copying needed: Everything is handled automatically

Version Control

Pull latest changes:
```
git pull
```
Add new tools: Copy to
```
scripts/
```
and run
```
./setup.sh
```
Update existing tools: Edit in place and commit changes
Share across machines: Push to remote and pull on other machines
Commit both: Source files AND synced
```
src/jk_tools/
```
files

Scratch Directory (Ephemeral Workspace)

Use a top-level

scratch/

directory in this repository for temporary experiments, throwaway scripts, notes, or generated files you do not want tracked by Git.

Why

Keeps the repo clean of WIP and exploratory artifacts
Avoids accidental commits of large or sensitive temporary files
Provides an easy, predictable location for ad-hoc work

Usage

mkdir -p scratch
cd scratch
# Create or copy experimental files here

You can freely create, modify, and delete anything inside

scratch/

without impacting version control. The path is ignored via

.gitignore

Guidelines

Never store the only copy of important work here—it's untracked
Safe to wipe/recreate at any time
Use subfolders if juggling multiple experiments
If something becomes valuable, move it into a tracked location (e.g.
```
scripts/
```
) before committing

Automation Tip

Add helpers or prototypes here first; once stable, promote them into

scripts/

and run

./setup.sh

Tools Repository

Related Skills

Nano Banana Pro

Markdown Converter

1password