db73cf5a39
Includes the current working directory changes. Historical commits and release binaries are excluded to limit Gitea storage. Source base: d7515973fbfd6dd2001fa156c483455b8081c7cb
22 lines
1.5 KiB
Markdown
22 lines
1.5 KiB
Markdown
# Commit message
|
|
|
|
For /FD-commit. Apply core scope, evidence, language, and protocol workflow rules. This entry drafts text.
|
|
|
|
## Scope and inspect
|
|
|
|
Accept a task, change scope, language/format request, or supplied diff. Otherwise use the single clear current task.
|
|
|
|
Check whether Git exists. If not, explain that a Git diff is unavailable; do not initialize a repository or invent changes. A user-supplied real diff can still support a message if its provenance is stated.
|
|
|
|
With Git, inspect staged/unstaged changes and relevant new files, read context, and follow existing message style. Do not infer functionality from filenames or include unrelated user/task changes.
|
|
|
|
Proceed only when ownership is clear. Clarify mixed changes, conflicts between staging and task scope, or an ambiguous target without altering the index. If no changes exist, report that.
|
|
|
|
## Output and boundaries
|
|
|
|
Write a concise Chinese title and, when useful, a body explaining the problem, change, and compatibility impact. Follow requested structure or existing conventions.
|
|
|
|
Describe actual changes rather than unfinished plans. Claim passing checks only after execution; accurately label failure, unrun checks, or limited validation when mentioned.
|
|
|
|
This command does not authorize staging, commits, pushes, branches, or releases. A separate explicit request for real Git operations follows the user's authorization, actual selected changes, and validation state; do not deny explicit instructions merely because drafting is this entry's default.
|