Menu
Generate a session changelog from git diff. Triggers on 'changelog', 'what changed', 'session summary', 'diff summary'.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Assign agents and skills to a plan's tasks, producing docs/plans/<feature>-dispatch.md. Run after /plan.
Run the full quality pipeline: lint, typecheck, and tests. Triggers on 'check', 'run checks', 'quality check', 'ci check'.
Pre-deployment audit: verify code quality, secrets, dependencies, and build. Triggers on 'deploy check', 'pre-deploy', 'deployment audit', 'ready to deploy'.
Maintain project documentation coverage: audit all components, update specific docs, or check coverage status. Triggers on 'docs audit', 'update docs', 'docs status', 'documentation coverage'.
Execute an approved dispatch plan task by task, producing docs/plans/<feature>-report.md. Run after /assign.
Configure OpenTelemetry export from Claude Code to a tracing backend (LangSmith, Langfuse, or Jaeger). Triggers on 'enable tracing', 'setup observability', 'configure otel', 'send traces'.
| name | changelog |
| description | Generate a session changelog from git diff. Triggers on 'changelog', 'what changed', 'session summary', 'diff summary'. |
| version | 0.1.0 |
Generate a changelog entry for the current session in Batch Creative Studio.
Gather changes
Run: git diff --stat HEAD~1..HEAD
If no commits yet in this session, use: git diff --stat
Categorize changes
Group files by type:
Then group by domain:
frontend: app/ (client UI), components/**, SSE client, visual languagebackend: app/api/**, orchestrator, retry engine, rate limiter, SSE server stream, blob signing, state store, failover engineproviders: lib/providers/**, adapters, provider config, reference normalizationtesting: **/*.test.ts, fixtures, fake providerdocs: docs/components/, docs/coverage.mdsecurity-backend: docs/security/**, SECURITY.mdWrite entry
Format as a markdown changelog entry:
## [Session] <YYYY-MM-DD>
### Added
- ...
### Changed
- ...
### Fixed
- ...
Focus on the why, not the what. Describe the purpose of changes, not just file names.
Output
Print the changelog entry to the terminal. Do not write to a file unless the user asks.