Menu
Suggest a Conventional Commits message for the last changes without committing. Analyzes the current diff and returns a ready-to-use commit name.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit that docs/rbac-permission-matrix.md matches the RBAC catalog in code (roles, permissions, and grants in rbac.constants.ts and api-contracts permissions.ts). Reports every mismatch.
Generate CRUD boilerplate (backend NestJS controller/service/module/guard/policy/factory/routes/e2e + frontend Redux slice/thunks/selectors/middleware/spi/api) from a given entity file and a list of methods.
Run the last steps before ending a feature. Shows a form where you can check/uncheck which final steps to run — update changelog, create a branch, run tests-parallel, create a PR — then executes the selected steps in that order.
Create a GitHub issue on bayesimpact/bayes-platform from a free-text description. Drafts a clear title and structured body, picks appropriate labels, and posts it via the gh CLI, returning the issue URL. Optionally enriches the issue with context from the current codebase.
Run Trivy vulnerability scan on Docker images (API, CPU workers, GPU workers). Builds images, scans for CRITICAL/HIGH CVEs, and reports findings.
Audit apps/web for the two paired rules from ADR 0010 — every `*.models.ts` has a sibling `*.factory.ts`, and every route registered in `{Scope}Routes.tsx` has a matching `stories/routes/{scope}/{Route}.stories.tsx`. Reports missing factories and missing route stories.
| name | commit-name |
| description | Suggest a Conventional Commits message for the last changes without committing. Analyzes the current diff and returns a ready-to-use commit name. |
| user_invocable | true |
Propose a commit message for the current changes following the Conventional Commits specification. Do NOT stage, commit, or modify any files — only output the suggested message.
<type>(<scope>): <short summary>
| Type | When to use |
|---|---|
feat | A new feature or capability |
fix | A bug fix |
refactor | Code change that neither fixes a bug nor adds a feature |
chore | Maintenance tasks, dependency updates, config changes |
ci | CI/CD pipeline, GitHub Actions, Makefile changes |
docs | Documentation only |
test | Adding or updating tests |
perf | Performance improvement |
style | Formatting, whitespace, linting (no logic change) |
core | Cross-cutting changes (changelog, versioning) |
Optional but encouraged. Use the domain or area affected:
AgentSession, Organization, Project, Userapi, web, ui, api-contractssecurity, docker, depsUse PascalCase for domain entities, lowercase for layers/infra. If the change spans many areas, omit the scope.
Run git status (never use -uall) and git diff in parallel to see the changes. If everything is already staged, use git diff --staged; if both staged and unstaged exist, look at both.
Analyze the diff and determine the type, optional scope, and a concise summary in imperative mood.
Output the suggested commit name in a code block so it is easy to copy. For non-trivial changes spanning multiple concerns, add a short body with - bullet points after a blank line.
If multiple distinct interpretations are reasonable, offer the best one first, then optionally 1–2 alternatives as a short list.
Do not run any git command that mutates state (git add, git commit, etc.).
feat(AgentSession): can delete
fix: show a loader when creating session
ci(security): add gitleaks allowlist
refactor(api): extract session validation into guard
test(web): add unit tests for project selector