Share general review and documentation rules

[onechat] / .agents / skills / issues / SKILL.md

diff --git a/.agents/skills/issues/SKILL.md b/.agents/skills/issues/SKILL.md
index 47672fcc3f3cf4dd9f3ead39d311ddc6f390d5db..7d64ac62c96b7a4f3e26a69487f7a90f069219e6 100644 (file)
--- a/.agents/skills/issues/SKILL.md
+++ b/.agents/skills/issues/SKILL.md
@@ -7,7 +7,9 @@ description: Read and write issues with git-bug. Use for any issue work.
 
 Issues live in git-bug, inside the Git repository, not in files. The
 `overview` issue lists the phases and the open decisions. Run the
-commands in the Nix development shell.
+commands in the Nix development shell. Internal git-bug tracker metadata
+commits may be unsigned, as the `commit` skill permits. Normal code and
+documentation commits still require signing and verification.
 
 ## Read
 
@@ -26,6 +28,8 @@ commands in the Nix development shell.
 - Format each body and comment with `mdformat -` in the repository, so
   that it uses `.mdformat.toml`. mdformat joins trailer lines into one
   line, so format the text first and add the trailers after it.
+- Quote a long text as a blockquote below the paragraph or list, not as
+  inline code. mdformat cannot wrap inline code.
 - Add a comment with `git bug bug comment new ID -m TEXT` for progress
   that matters: decisions made with the user, measurements, and checks
   that could not run.
@@ -58,7 +62,9 @@ that match any of the words, and it reads `Parent:` as a query
 qualifier. Nothing checks the trailers. Before you close a parent, make
 sure that its children are closed.
 
-Push the issues with `git bug push` when the repository has a remote.
+Push issues with `git bug push` only when the user authorizes it. A
+remote does not give permission to push. Do not rewrite published
+history without the user's explicit approval.
 
 This example creates an issue: