sonht1109/clone-code-changes

Clone Code Changes

Use this skill when the user requests to clone code changes from local repository to a new directory for review or testing.

Arguments

• now: The current timestamp in the format YYYYMMDD_HHmmss. Invent this value at runtime by running:

node -e "console.log(new Date().toISOString().replace('T', '_').replace(/[:.-]/g, '').replace('Z', ''))"

Notes

• cwd: The current working directory of the local repository where the user is running the commands (not .github directory). Must use this cwd for all file paths in the steps below.

Steps

Must follow these steps strictly in order:

1. Stage all code changes: Stage all changes in the local git repository to prepare for cloning. Run command:

git add -A && \
echo "=== STAGED FILES ===" && \
git diff --cached --stat && \
echo "=== METRICS ===" && \
git diff --cached --shortstat | awk '{ins=$4; del=$6; print "LINES:"(ins+del)}' && \
git diff --cached --name-only | awk 'END {print "FILES:"NR}'

2. Clone the changes: Run command to create a patch file with the staged changes into <cwd>/notes/code-changes/<now>/diff.patch.

First, create the directory for the code changes if it doesn't exist:

mkdir -p <cwd>/notes/code-changes/<now>

Then run command:

git diff --cached > <cwd>/notes/code-changes/<now>/diff.patch

3. Separate patch file: separate patch files for the code changes into multiple files to keep changes organized. Run script:

node <cwd>/.github/skills/clone-code-changes/scripts/separate-patch.js <now>

5. Provide confirmation: Inform the user that the code changes have been successfully cloned and provide the local path to the cloned code changes. Provide output following the specified format.

Output Format

Provide output in the following format:

The code changes have been successfully cloned.

- Code change patch directory: `<cwd>/notes/code-changes/<now>/contents`

Notes

• Stop and inform user if there are any errors during the process, especially when running the separate patch script.