document-changeslisted

# Document Changes Generate a structured markdown report documenting codebase changes from the current working session. The report captures files changed, commit history, and a human-readable summary suitable for team reviews, handoff documentation, or personal records. ## Arguments - `$ARGUMENTS` — Optional scope or description for the report (e.g., `"auth refactor"`, `"add OAuth2 support"`). Used to name the output file and populate the report's scope field. If not provided, scope is inferred from commit messages or changed file paths. ## Workflow Execute these 4 steps in order. **Stop early** if Step 1 or Step 2 determines there is nothing to report. --- ### Step 1: Validate Git Repository Verify the current directory is inside a git repository: ```bash git rev-parse --is-inside-work-tree ``` - If the command fails or returns `false`, stop and report: "Not inside a git repository. This skill requires git to gather change data." - If successful, continue to Step 2. --- ### Step 2: Gather Changes and Metadata Collect all change data by running these git commands. If any individual command fails, continue with the data that is available. #### 2.1 Repository Metadata ```bash git branch --show-current ``` ```bash git config user.name ``` ```bash git remote get-url origin 2>/dev/null ``` ```bash date "+%Y-%m-%d %H:%M %Z" ``` #### 2.2 Uncommitted Changes ```bash git status --porcelain ``` ```bash git diff --stat ``` ```bash git diff --name-status ``` #### 2