What is git-commit-angular?

A set of rules for writing Git commits in Angular style, a convention that labels changes such as features, fixes, tests, and documentation in a consistent format.

Use it to format commit subjects, scopes, descriptions, issue references, and breaking-change notices.

Consistent commit messages make a project's history easier to scan and help tools identify the kind of change made.

git-commit-angular — Cursor rule by rhyspenn

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 rules/rhyspenn/askme-cli/git-commit-angular

Clone the repo

git clone --depth 1 https://github.com/rhyspenn/askme-cli

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 835 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.00000	$0.00835
Opus 5	$0.00000	$0.00417
Sonnet 5	$0.00000	$0.00167
Haiku 4.5	$0.00000	$0.00084

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

Security

Grade A, and why

git-commit-angular 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.

.cursor/rules/git-commit-angular.mdc · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Commit 规范 (Angular Style)

本项目使用 Angular 提交规范来保持提交历史的一致性和可读性。

提交格式

<type>(<scope>): <subject>

<body>

<footer>

必需部分

Type (类型)

feat: 新功能
fix: Bug 修复
docs: 文档变更
style: 代码格式化（不影响代码运行的变动）
refactor: 重构（既不是新增功能，也不是修复bug的代码变动）
test: 增加测试
chore: 构建过程或辅助工具的变动
perf: 性能优化
ci: CI配置文件和脚本的变动
build: 影响构建系统或外部依赖的变动
revert: 回滚之前的提交

Subject (主题)

使用祈使句，现在时态："change" 而不是 "changed" 或 "changes"
首字母小写
结尾不加句号
限制在50个字符以内
清晰简洁地描述变更内容

可选部分

Scope (范围)

用括号包围，表示影响的模块或组件
例如：(components), (utils), (auth), (ui)
如果影响多个范围，可以用 * 表示

Body (正文)

详细描述变更的动机和前后对比
每行限制72个字符
可以包含多个段落

Footer (页脚)

用于关闭 Issue 或说明破坏性变更
Breaking Changes: BREAKING CHANGE: <description>
关闭 Issue: Closes #123, #456

示例

基本提交

feat: add user authentication
fix: resolve memory leak in data processing
docs: update API documentation
style: format code according to eslint rules
refactor: extract utility functions to separate module
test: add unit tests for user service
chore: update dependencies

带范围的提交

feat(auth): implement OAuth2 login
fix(components): resolve button click handler
docs(api): add endpoint documentation
style(ui): update button component styling
refactor(utils): simplify data validation logic

带正文的提交

feat(user): add profile management functionality

Allow users to update their profile information including
name, email, and avatar. Includes form validation and
error handling for better user experience.

Closes #42

破坏性变更

feat(api): change user authentication method

BREAKING CHANGE: The authentication API has been updated.
Users now need to use JWT tokens instead of session cookies.
Please update your client code accordingly.

提交检查清单

使用正确的 type
subject 简洁明了（≤50字符）
使用祈使句，现在时态
subject 首字母小写，无句号
如果需要，添加适当的 scope
复杂变更添加 body 说明
破坏性变更在 footer 中说明
关联相关的 Issue 编号

工具建议

Read the full file on GitHub · 122 lines

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 · 122 lines · 0 tokens per session scan A 1dd796f6b49d

Subscribe to this mod's changes

git-commit-angular is a cursor rule published in the GitHub repository rhyspenn/askme-cli (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 835 tokens. 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.

Git and workflow Testing Writing and docs mcp-server

git-commit-angular