refactor: emphasise reading, add trailer

Amolith created 

Change description from conditional to mandatory phrasing and add
Assisted-by trailer to formatted-commit usage example.

Assisted-by: GLM 4.7 via Crush <crush@charm.land>

Change summary

skills/formatting-commits/SKILL.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Detailed changes

skills/formatting-commits/SKILL.md 🔗 

@@ -1,6 +1,6 @@
 ---
 name: formatting-commits
-description: Creates commits strictly following Conventional Commits format. Use when committing changes, amending commits, or when the user mentions git commits, conventional commits, or commit messages.
+description: Creates commits strictly following Conventional Commits format. ALWAYS read BEFORE committing changes, amending commits, or when the user mentions git commits, conventional commits, or commit messages.
 compatibility: Requires `git` and `formatted-commit` CLI tools
 license: AGPL-3.0-or-later
 metadata:
@@ -28,7 +28,7 @@ Multi-line
 - Here
 
 EOF
-)"
+)" -T "Assisted-by: [Model] via [Agent]"
 </formatted-commit_example>
 
 Most source code repositories require both an appropriate prefix _and_ scope. Necessity of scope increases with repository size; the smaller the repo, the less necessary the scope. Valid trailers for ticket tracking integration depend on the platform in use.