提交
- 作者仓库星标 846
- 作者仓库 modbus
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @digitalpetri · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
You are tasked with creating git commits for the changes made during this session.
## Process
1. **Think about what changed:**
- Review the conversation history and understand what was achieved
- Run `git status` to see current changes
- Run `git diff` to understand the modifications
- Consider whether changes should be one commit or multiple logical commits
2. **Plan your commit(s):**
- Identify which files belong together
- Draft clear, descriptive commit messages
- Use imperative mood in commit messages
- Focus on why the changes were made, not just what
3. **Present your plan to the user:**
- List the files you plan to add for each commit
- Show the commit message(s) you'll use
- Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"
4. **Execute upon confirmation:**
- Use `git add` with specific files (never use `-A` or `.`)
- Create commits with your planned messages
- Show the result with `git log --oneline -n [number]`
## Remember
- You have the full context of what was done in this session
- Group related changes together
- Keep commits focused and atomic when possible
- The user trusts your judgment – they asked you to commit
- Write commit messages as if the user wrote them
章节与文件索引
按说明文件中的顺序排列。
工艺流程
记住
文件/命令 -> git status · git diff · git add · git log --oneline -n [number]
内容校验值 -> 55cf12ca2fd3
当前原文的自动摘译,尚未人工审校。
工艺流程
思考发生了什么变化: 查看对话历史记录并了解所实现的目标 运行
git status以查看当前更改 运行git diff以了解修改 考虑更改应该是一次提交还是多次逻辑提交记住
您拥有本次会话中所做操作的完整上下文 将相关更改分组在一起 尽可能保持提交的重点和原子性 用户信任您的判断 – 他们要求您提交 编写提交消息,就像用户编写它们一样