A code-review preparation workflow covering quality checks, conventional commits, branches, and pull requests. A conventional commit uses a standard format such as `fix(scope): message`.

Use it when preparing changes for review, running the required checks, creating commits, pushing a branch, or opening a pull request.

It provides a consistent path from unfinished changes to a tested, reviewable pull request.

commit — Skill by decocms

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/decocms/studio/commit

Any agent

npx skills add decocms/studio --skill commit

Clone the repo

git clone --depth 1 https://github.com/decocms/studio

Made for: Claude Code, Codex.

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 367 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00045	$0.00367
Opus 5	$0.00023	$0.00183
Sonnet 5	$0.00009	$0.00073
Haiku 4.5	$0.00005	$0.00037

Measured yesterday against content hash 8700361f43a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/commit/SKILL.md · 41 lines

What it actually says

I'm getting ready for code review. Please follow these steps:

0. Branch Check

If you're on the main branch, create a new feature branch first before making any commits.

1. Quality Assurance Checks

Run the following commands in order:

bun run fmt
bun run lint
bun run check:ci
bun run knip
bun test

If any checks fail, address the issues before proceeding.

2. Create Commits

Split the file changes into logical commits following Conventional Commit format:

type(scope): message (e.g., feat(chat): add thread deletion, fix(auth): resolve token expiry)
Use types: feat, fix, refactor, docs, chore, test, etc.

Push all commits to the remote branch.

3. Create or Update Pull Request

Use the gh CLI tool to create or update the PR. The PR description MUST follow the structure defined in .github/pull_request_template.md.

Important:

Read .github/pull_request_template.md and follow its structure exactly
Analyze the git diff and commits to generate accurate content for each section
For "How to Test", provide specific, actionable steps based on the actual changes
Mark "N/A" for Screenshots and Migration Notes if not applicable
Ensure the PR title follows Conventional Commit format

4. Report Results

Finally, report the GitHub PR URL.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 41 lines · 45 tokens per session scan A 8700361f43a9

Subscribe to this mod's changes

commit is a skill published in the GitHub repository decocms/studio (401 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 367 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Data and AI Git and workflow LLM agents ai bun deco mcp

opengeni

Use when editing, operating, extending, documenting, or debugging the OpenGeni source repository or deployment: architecture, sessions/events, worker orchestration, sandbox backends, files/storage, tools/MCP, scheduling, configuration, and deployment. For a customer product that consumes a standalone OpenGeni…

Cloudgeni-ai/opengeni · 81 tokens

refactor-module

Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.

Cloudgeni-ai/opengeni · 28 tokens

terraform-search-import

Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.

Cloudgeni-ai/opengeni · 39 tokens

checkov

Use Checkov to scan Terraform and infrastructure-as-code repositories for policy violations, explain findings, choose safe fixes, rerun scans, and prepare pull requests with remediations.

Cloudgeni-ai/opengeni · 38 tokens

document-parsing

Extract readable Markdown from local Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and text-based PDF files using the preinstalled AnyDoc runtime.