From hermit-scribe
One-time setup for hermit-scribe: appends the Issue Filing block to CLAUDE.md and seeds auto-mode config for api.github.com. Run once per project; re-run after upgrade.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hermit-scribe:hatchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
hermit-scribe is a maintainer utility with a single skill (`/hermit-scribe:hermit-scribe`) — this hatch only needs to make its GitHub App posting behavior visible to the operator's `CLAUDE.md` and to Claude Code's auto-mode classifier. There is no config, no routines, no channels.
hermit-scribe is a maintainer utility with a single skill (/hermit-scribe:hermit-scribe) — this hatch only needs to make its GitHub App posting behavior visible to the operator's CLAUDE.md and to Claude Code's auto-mode classifier. There is no config, no routines, no channels.
Check if .claude-code-hermit/ exists in the current project.
AskUserQuestion) "Core hermit isn't set up yet. Run /claude-code-hermit:hatch now?" with options Yes — run now / No — I'll do it later. If yes, invoke /claude-code-hermit:hatch via the Skill tool and stop. If no, stop.Resolve target file: read .claude-code-hermit/state/hatch-options.json. "target": "local" → CLAUDE.local.md; "target": "committed" or the file absent → CLAUDE.md.
Read target_file (a missing file is marker-absent — the append below will create it). Look for the marker <!-- hermit-scribe: Issue Filing -->.
${CLAUDE_PLUGIN_ROOT}/state-templates/CLAUDE-APPEND.md to target_file (create the file if it doesn't exist).Run bun ${CLAUDE_PLUGIN_ROOT}/scripts/automode-env.ts .claude/settings.local.json — always .claude/settings.local.json, regardless of hatch_target: Claude Code's auto-mode classifier reads autoMode config only from local/user scope, never a committed project .claude/settings.json. This names api.github.com (scoped to the configured HERMIT_GH_REPO, or the default gtapps/claude-code-hermit) as a service the hermit posts to only with the operator's in-session confirmation — context for the classifier, not a standing permission grant (filing still goes through the skill's own preview/confirm gate every time). Additive and idempotent; safe to re-run. No prompt needed.
Print: "hermit-scribe active. Issue filing goes through /hermit-scribe:hermit-scribe, always with an in-session preview before posting."
npx claudepluginhub p/gtapps-hermit-scribe-plugins-hermit-scribeSets up dev safety rules, git-push-guard hook, and companion skills for a project. Run once after initializing the core hermit plugin.
Interactive wizard configures repositories for Claude Code best practices by creating CLAUDE.md, slash commands, agents, hooks, and permissions. Activates on 'setup claude', 'init claude', or repo setup requests.
Generates or audits a CLAUDE.md for a project by combining data from Repo Auditor with a guided developer interview.