Borrowing it
Nothing to install: this file belongs to gurezo/web-serial-rxjs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gurezo/web-serial-rxjs/main/.cursor/skills/conventional-commits/SKILL.mdgit clone --depth 1 https://github.com/gurezo/web-serial-rxjsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gurezo/web-serial-rxjs/conventional-commits)<a href="https://agentmods.dev/skills/gurezo/web-serial-rxjs/conventional-commits"><img src="https://agentmods.dev/badge/skills/gurezo/web-serial-rxjs/conventional-commits.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00058 | $0.00856 |
| Opus 5 | $0.00029 | $0.00428 |
| Sonnet 5 | $0.00012 | $0.00171 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
conventional-commits 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 8d ago.
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.
What it actually says
Conventional Commits for web-serial-rxjs
このリポジトリ（TypeScript ライブラリ + RxJS + Nx Workspace）向けに、Conventional Commits 準拠の commit message / PR title を生成・検証するための Skill。
目的
- commit message と PR title を Conventional Commits に統一する。
packages/web-serial-rxjsとapps/example-*の構成に整合する scope を選ぶ。- AI が生成するメッセージの品質を安定化させる。
形式
<type>(<scope>): <summary>
[optional body]
[optional footer(s)]
適用ルール
- type は小文字 で、許可された値のみを使う (
feat,fix,docs,style,refactor,perf,test,build,ci,chore,revert)。 - scope は小文字、ハイフン区切り。
commitlint.config.jsのscope-enumまたはscopes.mdから選ぶ。 - summary は英語、命令形 (imperative mood)。先頭は小文字、末尾にピリオドを付けない。
- summary は 72 文字以内。
- type と変更内容を一致させる。フォーマット変更のみは
style、CI 設定はci。 - 関連性のない変更を 1 つのコミットに混在させない。
- breaking change は footer に
BREAKING CHANGE:を記載する (type!表記は使わない)。
Nx を踏まえた scope 選択
- ライブラリ本体 (
packages/web-serial-rxjs) の変更 →web-serial-rxjs。 - 各 example アプリの変更 → 対応する
example-*scope。 - ルート設定・複数 project に跨る変更 →
workspace。 - ドキュメント全般 →
docs/readme。 - GitHub Actions →
ci。 - 依存・ビルド設定 →
build/chore/deps。
詳細は scopes.md と .cursor/rules/nx/30-nx-project-scope.mdc を参照。
docs / ci / build / chore の使い分け
| 種別 | type | 例 |
|---|---|---|
| README / CONTRIBUTING 等のドキュメント | docs |
docs(workspace): update readme quick start |
| GitHub Actions ワークフロー追加・変更 | ci |
ci(workspace): update npm publish workflow |
| 依存追加・更新、ビルド設定 | build |
build(workspace): bump nx dependency |
| 上記に当てはまらない雑務 | chore |
chore(workspace): remove unused script |
参照ファイル
examples.md: 良い例と悪い例assertions.md: 検証項目と Valid / Invalid サンプルscopes.md: scope 一覧と用途- リポジトリ側:
.cursor/rules/commits/,commitlint.config.js,CONTRIBUTING.md
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 62 lines · 58 tokens per session scan A 2c2d9ce2adc3
conventional-commits is a skill published in the GitHub repository gurezo/web-serial-rxjs (2 stars, last pushed 10d ago), licensed MIT. It adds 58 tokens to every session and 856 once invoked, about $0.0003 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-31.
Other skills, from other repositories
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.