القائمة
Use when the user says "draft release notes", "/release-notes", or "changelog for v<x>". Generates release notes from a git range by grouping commits/PRs into Features, Fixes, and Chores.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when reviewing a backend HTTP / GraphQL handler for validation, authz, errors, performance, observability, and security, or "/backend-review". Produces a structured review with file:line citations.
Use when running a cloud security posture scan (CSPM) on AWS, Azure, or GCP using prowler, scout-suite, or checkov, or "/cloud-scan". Requires read-only credentials; produces CIS-benchmark-aligned findings with remediation.
Use when scanning a container image or Dockerfile for vulnerabilities, misconfigurations, and best-practice violations using trivy, dockle, or hadolint, or "/image-scan". Flags base-image CVEs, root user, missing healthchecks, and bloat.
Use when running an authorized non-intrusive DAST baseline scan (OWASP ZAP baseline, nuclei, nikto) against a web app or API endpoint you own, or "/dast". Requires explicit authorization; refuses unowned targets.
Use when handed a stack trace, error log, or "this is broken" with a paste of output, and asked to find the root cause across frontend, backend, or DB tiers, or "/debug-trace". Produces a hypothesis tree, the evidence supporting each branch, and the next diagnostic step.
Use when scanning a project's third-party dependencies for known CVEs across npm, pip, Go, Maven, Cargo, etc., or "/dep-scan". Runs trivy, npm audit, pip-audit, govulncheck, or osv-scanner and produces a prioritized fix list.
| name | release-notes |
| description | Use when the user says "draft release notes", "/release-notes", or "changelog for v<x>". Generates release notes from a git range by grouping commits/PRs into Features, Fixes, and Chores. |
git describe --tags --abbrev=0).HEAD.Resolve range: FROM..TO.
Collect commits:
git log FROM..TO --no-merges --pretty=format:'%H%x09%s%x09%an'
Map commits to PRs using gh pr list --search "<sha>" --state merged --json number,title,labels,author.
Classify by conventional-commit prefix or PR labels:
feat: or label feature → Featuresfix: or label bug → Fixesperf: → Performancedocs:, chore:, refactor:, test: → Chores! or BREAKING CHANGE:) → Breaking changes (top of list).Render:
## v<VERSION> — <YYYY-MM-DD>
### Breaking changes
- <title> (#<pr>) — @<author>
### Features
- ...
### Fixes
- ...
### Performance
- ...
### Chores
- ...
**Full changelog:** <FROM>...<TO>
Offer to write to CHANGELOG.md or create a GitHub Release with gh release create.
wip / fixup!.