chore: remove the false --body-file rule from the user-level groom-issue skill

Aperta
  • Qualcosa non va?
#455 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
1/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Ambito
tooling

Direzione di ricerca

The issue identifies two passages in the user-level groom-issue skill file, ~/.claude/skills/groom-issue/SKILL.md, and gives their exact wording. Read those passages and remove the inline-body prohibition and its stated reason, while retaining the file-based gh issue edit <N> --body-file <temp-file> step. Done when the acceptance criteria hold and the groomed marker and heading names are unchanged.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Found while auditing the pipeline for #400 (piece 2). This is a fix to a file on the owner's machine, not a change in this repo, so there is no PR.

Problem

The user-level skill ~/.claude/skills/groom-issue/SKILL.md carries the --body-file rule that #400 cut everywhere else. The stated reason ("inline bodies and heredocs mangle backticks, angle brackets, pipe characters, and $") is wrong for Git Bash: a heredoc with a quoted delimiter passes those characters through unchanged. The only real mangle is an argument that starts with /. See the #400 decisions comment (piece 2, "--body-file rule cut everywhere"): https://github.com/nevridge/TaskFlow/issues/400#issuecomment-6697965229. That comment lists groom-issue and pr-triage as the two user-level skills edited by hand. The pr-triage half is scope item 6 of #432.

Two places in the file:

  • Line 111: "Delete the temp file afterward. Never pass the body inline via --body — inline bodies and heredocs mangle backticks, angle brackets, pipe characters, and $."
  • Line 137, in the rules list: "All gh body arguments use --body-file, never --body. Write to a temp file, pass --body-file, then delete the temp file."

Change

  1. Delete the line 137 bullet.
  2. In line 111, delete the "Never pass the body inline ... mangle ..." sentence. Keep the step above it (write the assembled body with the Write tool, then gh issue edit <N> --body-file <temp-file>): a long groomed body is simpler to pass from a file, and pr-triage keeps --input <file> for the same reason. Say it as a method, not as a rule with a false reason.
  3. If a failure shows up later, put back one line with the real reason.

Acceptance criteria

  1. ~/.claude/skills/groom-issue/SKILL.md no longer says to never pass a body inline, and no longer gives the mangling reason.
  2. The step that writes the body to a file and runs gh issue edit <N> --body-file still works as before.
  3. No other change to the skill, in particular the groomed marker on the first line and the heading names.

Out of scope

  • The pr-triage edits (#432), the spec-writer dead tools (#430) and the ux-test audit (#431).
Lingua principale
C#
Stelle
1
Fork
0
Merge medio
2h 2m
PR unite (30g)
98

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nevridge/TaskFlow

Tutte le issue di nevridge/TaskFlow

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.