Local Code Release Assistant

Prepare a structured delivery report from a local Git repository without uploading repository content.

Workflow

Identify the target repository and whether to inspect all working-tree changes or staged changes only. Ask only when the user's intent cannot be inferred.
From this skill's directory, run scripts/generate_report.py and pass the target with --repo:
```
python scripts/generate_report.py --repo /path/to/repository --mode pr --output pr_report.md
```
Add --staged when the user asks about staged or commit-ready changes.
Select the mode that matches the requested deliverable:
- pr for a pull-request description.
- release for release notes and rollback guidance.
- review for change-review risks and test suggestions.
Read the generated Markdown, preserve evidence-based findings, and adapt its wording to the user's requested language or repository conventions.
Tell the user where the report was written and call out unresolved questions or truncated analysis.

Work only with local Git data by default; do not upload source code or credentials.
Never include environment variables, credentials, or full absolute paths in reports.
If no changes are found, explain that no report was generated and suggest checking the branch or staged scope.
Prefer concrete observations from changed files and diff content over generic statements.
Do not claim that tests passed, deployment succeeded, or rollback is safe unless there is direct evidence.
If the script cannot run, use git status --short, git diff --stat, git diff, and git log -5 --oneline to prepare the same report sections manually.