Menu
Generate a commit message for the current staged changes and commit
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
Run a full code review of the current change — fan out every relevant review concern across independent subagents (the local review skills plus the ably-skills code-review-* plugin) and synthesise one consolidated report. Read-only; never edits code.
Audit whether the demos under demo/ are still current with a change — they compile against and use the changed public API correctly, showcase new or renamed capabilities, and keep their e2e test coverage current. Read-only; produces a conformance report and never edits code.
Review documentation for accuracy, completeness, and conformance to the project's doc standards — whether a code change left docs/ stale or incomplete, or as the review half of the docs writing loop. Read-only; produces a conformance report and never edits code or docs.
Audit whether changed code conforms to the project's own rules in .claude/rules/ and the conventions in CLAUDE.md. Read-only; produces a conformance report and never edits code.
Audit whether the .claude/rules/* guidance still matches the code after a change — stale conventions, drifted examples, rules describing removed behaviour, or new conventions the change introduces that a rule should capture. Read-only; produces a conformance report and never edits code or rules.
Write or improve markdown documentation for the AI Transport SDK. Follows the project's doc principles (atomic pages, problem-first framing, one path then depth) and the established style from the docs that received positive feedback.
| name | commit |
| description | Generate a commit message for the current staged changes and commit |
| allowed-tools | Skill, Bash(git diff *), Bash(git status), AskUserQuestion |
This skill runs the shared ably-skills:git-commit workflow, with the
project-specific additions below layered on top.
These rules are specific to this repository. They take precedence over the general guidance in the shared skill when writing the commit message:
Jira tickets: do NOT include the ticket ID in the summary line.
Add it on its own line at the end of the body in square brackets
(e.g. [PUB-123]).
Component prefix: begin the summary with a lowercase prefix naming
the architectural area the change relates to, followed by : and a
lowercase, imperative description. For example,
transport: extract shared session lifecycle helpers. The prefix names the
area, not the file path.
codec:, transport:, react:, vercel:, docs:,
demos:, shared:, project:.tree:, view:, clientSession:,
agentSession:, runManager:, chatTransport:.vercel codec:.claude/skills:,
claude/rules:.If changes span multiple unrelated areas, pick the most significant one or use a broader prefix.
Invoke the ably-skills:git-commit skill with the Skill tool and follow its
steps in full (gather context, determine intent, generate message, present,
confirm, commit), applying the project-specific rules above when writing the
message.