Borrowing it
Nothing to install: this file belongs to zwl467135974/lumina. 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/zwl467135974/lumina/master/.agents/skills/lumina_git_commit/SKILL.mdgit clone --depth 1 https://github.com/zwl467135974/luminaWrote 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/zwl467135974/lumina/lumina_git_commit)<a href="https://agentmods.dev/skills/zwl467135974/lumina/lumina_git_commit"><img src="https://agentmods.dev/badge/skills/zwl467135974/lumina/lumina_git_commit.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.02618 |
| Opus 5 | $0.00019 | $0.01309 |
| Sonnet 5 | $0.00008 | $0.00524 |
| Haiku 4.5 | $0.00004 | $0.00262 |
Grade A, and why
lumina_git_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 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.
How it starts
The opening of the file, as written. The whole thing — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lumina Git Commit 信息生成规范
功能概述
本技能包用于为 Lumina 框架项目的 Git 暂存区变更生成规范化的提交信息，确保提交历史清晰、可追溯、便于维护。
Commit 信息格式规范
标准格式
<type>(<scope>): <subject>
<body>
<footer>
类型 (Type)
| 类型 | 说明 | 使用场景 | 示例 |
|---|---|---|---|
| feat | 新功能 | 添加新功能、新特性 | feat: 新增用户管理功能 |
| fix | 修复 | 修复 bug | fix: 修复登录状态过期问题 |
| docs | 文档 | 仅文档变更 | docs: 更新 API 文档 |
| style | 格式 | 代码格式调整，不影响逻辑 | style: 格式化代码 |
| refactor | 重构 | 代码重构，不改变功能 | refactor: 重构用户服务层 |
| perf | 性能 | 性能优化 | perf: 优化查询性能 |
| test | 测试 | 添加或修改测试 | test: 添加用户服务单元测试 |
| chore | 构建/工具 | 构建流程、工具链变更 | chore: 更新依赖版本 |
| build | 构建 | 构建系统变更 | build: 配置 Maven 打包 |
作用域 (Scope)
可选字段，用于标识变更影响的范围：
- 模块名:
agent-core,business-base,gateway,framework - 功能域:
user,role,permission,tenant - 技术域:
api,service,config,security
示例：
feat(agent-core): 新增工具适配器fix(business-base): 修复租户拦截器问题
主题 (Subject)
- 必填: 简短描述变更内容
- 格式: 使用中文，首字母小写，结尾不加句号
- 长度: 不超过 50 个字符
- 风格: 使用祈使语气，如"新增"、"修复"、"优化"
正文 (Body)
可选，详细描述变更：
- 为什么: 说明变更的原因和背景
- 怎么做: 简要说明实现方式
- 影响: 说明对系统的影响
格式要求：
- 每行不超过 72 个字符
- 使用空行分隔段落
- 使用列表展示多个变更点
页脚 (Footer)
可选，用于：
- 关联 Issue:
Closes #123,Fixes #456 - 破坏性变更:
BREAKING CHANGE: API 接口变更 - 影响模块:
Affects: agent-core, business-base
Commit 信息结构模板
单功能提交
feat(scope): 简短描述
详细说明变更内容，可以包含：
- 变更点1
- 变更点2
- 变更点3
多模块提交
feat: 主要功能描述
## 主要变更
### 模块1
- 变更点1
- 变更点2
### 模块2
- 变更点1
- 变更点2
## 统计数据
- X 个文件变更
- 新增 Y 行代码
- 删除 Z 行代码
修复提交
fix(scope): 修复问题描述
修复的问题：
- 问题1描述
- 问题2描述
解决方案：
- 解决方式1
- 解决方式2
Closes #issue-number
分析暂存区变更的步骤
1. 获取变更统计
git status # 查看暂存文件列表
git diff --cached --stat # 查看变更统计
git diff --cached --shortstat # 查看简短统计
2. 分析变更类型
根据暂存文件判断变更类型：
- 新增文件 (
new file): 通常是feat或docs - 修改文件 (
modified): 可能是fix,refactor,perf,feat - 删除文件 (
deleted): 可能是refactor或chore
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 · 356 lines · 38 tokens per session scan A e6b14f27c2c0
lumina_git_commit is a skill published in the GitHub repository zwl467135974/lumina (65 stars, last pushed 18d ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,618 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.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…