From 46646c83374b8ad22b98a97d5c7d795c5944e3d7 Mon Sep 17 00:00:00 2001 From: "Anderson A. Giacomolli" Date: Fri, 6 Nov 2026 15:54:56 -0300 Subject: [PATCH] Format issue bodies and comments with mdformat Issue bodies and comments go through mdformat with the repository configuration, so they wrap and number lists as every other Markdown file does. mdformat joins trailer lines into one line, so the text is formatted first and the trailers are added after it. --- .agents/skills/issues/SKILL.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.agents/skills/issues/SKILL.md b/.agents/skills/issues/SKILL.md index f782536..47672fc 100644 --- a/.agents/skills/issues/SKILL.md +++ b/.agents/skills/issues/SKILL.md @@ -23,6 +23,9 @@ commands in the Nix development shell. imperative mood, with no final period. - Write the body in Markdown. State the result for the user, the scope, and how to check it. +- 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. - 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. @@ -60,6 +63,9 @@ Push the issues with `git bug push` when the repository has a remote. This example creates an issue: ```sh +body=$(mdformat - < body.md) git bug bug new --non-interactive -t 'Decide the root wake interval' \ - -m "$(cat body.md)" + -m "$body + +Parent: 180a674" ``` -- 2.53.0