Skip to content
Back to skills

Scribe

ASecurity

Route mechanical git prose — commit messages, PR titles/bodies, release notes, changelog entries — to the cheapest healthy model (free local ollama first) instead of burning main-session tokens. Use whenever the user asks to commit, open a PR, cut a release, or write a changelog and the prose can be drafted from the diff/log. The advisor writes text only (read-only); YOU run the git/gh commands.

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 5, 2026
ai-agentsgobashnodegit

Works with

  • claude code

Security analysis

A100/100

Scanned September 5, 2026

npx -y skills add kimmingul/xllm --skill scribe --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Scribe?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Scribe
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kimmingul-scribe/badge)](https://www.skillsdirectory.com/skills/kimmingul-scribe)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: scribe
description: >
  Route mechanical git prose — commit messages, PR titles/bodies, release
  notes, changelog entries — to the cheapest healthy model (free local ollama
  first) instead of burning main-session tokens. Use whenever the user asks to
  commit, open a PR, cut a release, or write a changelog and the prose can be
  drafted from the diff/log. The advisor writes text only (read-only); YOU run
  the git/gh commands.
---

# scribe — Cheap-prose lane for git chores (xllm)

Split of labor: deterministic collectors gather the diff/log (no LLM), the
**cheapest healthy advisor** writes only the prose, and **you** execute the
git command. push/tag are pure mechanics — no model call at all.

## Resolve the script

Claude Code: `"${CLAUDE_PLUGIN_ROOT}/scripts/xllm-scribe.js"`.
Other hosts: `<plugin-root>/scripts/xllm-scribe.js` (two directories above
this SKILL.md).

## Run (Bash tool)

```bash
node <xllm-scribe.js> commit                      # staged diff → commit message
node <xllm-scribe.js> pr --base main              # commits+diffstat → PR title/body
node <xllm-scribe.js> release --from v0.5.0       # log range → release notes
node <xllm-scribe.js> notes --from v0.5.0         # log range → changelog entry
# all accept --provider <spec> to override routing
```

Message arrives on **stdout** (diagnostics on stderr), so:

```bash
MSG=$(node <xllm-scribe.js> commit) && git commit -m "$MSG"
```

## Contract

- Routing: `scribe` role — local-first (free), `release`/`notes` auto-escalate
  to a cloud model when one is healthy (narrative needs judgment). Pin per
  project: `--set-role scribe ollama:qwen3.6:latest@low`.
- Output is validated deterministically (Conventional Commits format, subject
  ≤72 chars, no fences, no invented facts instruction) with one corrective
  retry; **exit 3** means validation failed — show the raw text to the user
  for review instead of using it blindly.
- Privacy: the diff goes only to the routed advisor and is **never persisted**
  by xllm (no artifact) — the git object itself is the record. For sensitive
  repos keep scribe on local models.
- Show the generated message to the user (or apply directly if they asked you
  to commit), then run the git command yourself. xllm never runs git.
- Advisors stay read-only throughout — this lane generates text, nothing else.

## When NOT to use

- push / tag creation → pure git commands; no model needed at all.
- Release strategy, breaking-change judgment, "should we ship" → that is
  analysis, not scribing; use `ask`/`review roles` with a strong model.
- If no advisor is healthy: on Claude Code, spawn a host-native cheap-model
  subagent instead (Agent tool with `model: haiku` — pass it the same
  collector output and template contract); otherwise write the prose yourself.
  Never block the user on a missing advisor.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.