Script Git Manager Skill

---

name: script-git-manager

description: >

Create and modify scripts in ~/.nanobot/workspace/test with strict Git versioning.

Each script lives in its own directory with an isolated git repository.

Always confirms creation plan before execution and reports progress at each step.

Uses ~/.nanobot/workspace/venv for Python environment and package management.

---

# Script Git Manager Skill

This skill enforces a strict, deterministic workflow for creating and modifying scripts,

using Git as the sole state memory.

It is designed to prevent accidental file creation, uncontrolled refactors,

and loss of history.

---

Scope

---

Python Environment

All Python-related operations (pip install, script execution) must use the virtual environment:

# Activate virtual environment
source ~/.nanobot/workspace/venv/bin/activate

# Install packages
pip install <package_name>

# Execute Python scripts
python <script_path>

# Deactivate when done
deactivate

**Always activate the venv before any pip or python command.**

---

Creation Workflow

Use this skill **only when the user explicitly asks to create a new script**.

Phase 1: Plan Confirmation

Before creating anything, present a detailed creation plan to the user:

📋 Script Creation Plan for: <script_name>

Directory: ~/.nanobot/workspace/test/<script_name>
File: <script_name>.<extension>
Language: <language>
Dependencies: <list of required packages, or "None">

Steps to execute:
1. Create directory ~/.nanobot/workspace/test/<script_name>
2. Initialize Git repository
3. Create script file <script_name>.<extension>
4. [If Python with dependencies] Activate venv and install: <packages>
5. Write script content
6. Create initial Git commit

Proceed with this plan? (yes/no)

**Wait for explicit user confirmation before proceeding.**

Phase 2: Step-by-Step Execution

Execute each step sequentially and report progress after each one:

**Step 1: Create directory**

cd ~/.nanobot/workspace/test
mkdir <script_name>

Output: `✓ Created directory: ~/.nanobot/workspace/test/<script_name>`

**Step 2: Initialize Git**

cd <script_name>
git init

Output: `✓ Initialized Git repository`

**Step 3: Create script file**

touch <script_name>.<extension>

Output: `✓ Created file: <script_name>.<extension>`

**Step 4: Install dependencies (if Python with dependencies)**

source ~/.nanobot/workspace/venv/bin/activate
pip install <package1> <package2> ...
deactivate

Output: `✓ Installed Python packages: <package_list>`

**Step 5: Write script content**

# Write the actual script code to the file

Output: `✓ Script content written (<X> lines)`

**Step 6: Create initial commit**

git add .
git commit -m "Initial commit: <script_name>"

Output: `✓ Initial Git commit created`

**Final summary:**

✅ Script created successfully!

Location: ~/.nanobot/workspace/test/<script_name>/<script_name>.<extension>
Git status: Clean (1 commit)
[If Python] Virtual environment: ~/.nanobot/workspace/venv

---

Modification Workflow

Use this skill **only when the user asks to modify an existing script**.

Phase 1: Plan Confirmation

Before modifying, present the modification plan:

📝 Script Modification Plan for: <script_name>

Location: ~/.nanobot/workspace/test/<script_name>/<script_file>
Changes requested: <summary of user's request>

Steps to execute:
1. Enter script directory
2. Create checkpoint commit (current state)
3. Apply modifications: <specific changes>
4. [If new Python dependencies] Install via venv: <packages>
5. Commit changes with message: "<description>"

Proceed with this plan? (yes/no)

**Wait for explicit user confirmation before proceeding.**

Phase 2: Step-by-Step Execution

**Step 1: Enter directory**

cd ~/.nanobot/workspace/test/<script_name>

Output: `✓ Entered script directory`

**Step 2: Create checkpoint**

git add .
git commit -m "Checkpoint before modification"

Output: `✓ Checkpoint commit created`

**Step 3: Apply modifications**

# Modify the script file as requested

Output: `✓ Modifications applied to <script_file>`

**Step 4: Install new dependencies (if applicable)**

source ~/.nanobot/workspace/venv/bin/activate
pip install <new_package>
deactivate

Output: `✓ Installed new packages: <package_list>`

**Step 5: Commit changes**

git add .
git commit -m "<concise description of the change>"

Output: `✓ Changes committed: "<commit_message>"`

**Final summary:**

✅ Script modified successfully!

Location: ~/.nanobot/workspace/test/<script_name>/<script_file>
Changes: <brief summary>
Git commits: 2 new commits (checkpoint + modification)

---

Hard Constraints (Must Never Be Violated)

---

Decision Rules

---

Progress Reporting Format

Use these symbols for consistency:

Each step output should be concise (1-2 lines) but informative.

---

Philosophy

Git is the memory.

The filesystem is the contract.

Confirmation prevents mistakes.

Transparency builds trust.

The venv isolates dependencies.