hermit-scribe

hermit-scribe

Files a GitHub issue or posts a comment on an existing issue via a configured GitHub App bot identity.

When to activate (filing)

Activate when the operator says:

• "file PROP-NNN as a GH issue"
• "open an issue for this"
• "report this to the tracker"
• "file a GH issue for [description]"

When to activate (commenting)

Activate when the operator says:

• "add a comment to issue #NNN"
• "comment on #NNN: [text]"
• "reply to issue #NNN"

How to file

Step 1: resolve content.

If the operator named a proposal (PROP-NNN):

1. Glob .claude-code-hermit/proposals/PROP-NNN-*.md to find the file.

2. Read frontmatter: id, title, category, session.

3. Read body sections: ## Context, ## Problem, ## Proposed Solution, ## Impact.

4. Derive the Conventional-Commits type, scope, and labels. Write the raw (pre-translation) frontmatter title and proposal body to temp files, then run:

   bun "${CLAUDE_SKILL_DIR}/file-issue.ts" classify {category} {title-file} {body-file}
   

   It emits JSON {type, scope, labels, title_line} — title_line is <type>(<scope>): <title> (scope omitted when unresolved). Review it, then use title_line as the draft title and hold labels for Step 6. (Scope resolution reads _hermit_versions from .claude-code-hermit/config.json; hermit-filed is added by the script — it is not in labels.)

5. Construct draft body with the four body sections. The provenance footer (see Step 3) is NOT part of the draft — appending it here would expose proposal={id} to the sanitizer, which would redact it as operator-project detail and break dedup.

For ad-hoc issues (no proposal): use the title and body the operator provides verbatim — no CC type/scope construction.

Then, for both proposal-backed and ad-hoc issues:

Step 1b: language normalization.

If the title or body is not already in English, translate to English. Preserve verbatim:

• Technical identifiers (entity IDs, API names, file paths, function names, package names, plugin slugs, repo names)
• Code blocks and command lines
• Frontmatter field names and values
• Proper nouns