h8nc4y
UserAgent skill for Claude Code and Codex: idempotently replace-or-append a Markdown section without corrupting code fences - fence-aware heading scans, fixed-marker boundaries, and an apply-twice-diff-zero verification recipe, with a tested reference implementation.
Categories
Indexed Skills (4)
markdown-idempotent-section-merge
Idempotently replace-or-append one Markdown section (a "## Heading" block) without corrupting code fences. Use on symptoms like: an automated section merge duplicated the section on every run, a replace range was cut short at a "##" line inside a code fence, a heading inside a code fence was treated as the next section boundary, a "###" subheading ended the section early, a README / AGENTS.md / CLAUDE.md updater never converges (the second run still changes the file), or a leftover fence swallowed the rest of the document after a bad merge. Covers fence-aware heading scanning, fixed begin/end marker boundaries, the single-H2 invariant (^##[^#]), and an apply-twice-diff-zero verification recipe with a tested reference implementation.
windows-utf8-text-hygiene
Normalize and verify text-file encodings on Windows, especially Japanese content: repo text = UTF-8 without BOM, LF, no trailing whitespace, no NUL bytes. Use on symptoms like mojibake / garbled Japanese (文字化け), a UTF-8 BOM appearing in diffs, CRLF creeping into a repo, git diff --check trailing-whitespace warnings, ripgrep saying "binary file matches" (a NUL byte) or "pattern contains \0 but it is impossible to match", Windows PowerShell 5.1 breaking on a BOM-less UTF-8 .ps1 with Japanese comments (parse errors or silently skipped statements), PowerShell backtick expansion turning `t / `f into TAB / form feed inside generated Markdown, or hook stdout emitting garbled Japanese. Includes a strict UTF-8 decode guard (DecoderFallbackException) that stops lenient reads from irreversibly destroying ANSI / CP932 (Shift_JIS) files via silent U+FFFD replacement.
agent-handoff-docs
Documentation framework for multi-session, multi-agent development — how to structure project docs so the next agent (or human) picks up work cold. A four-document split with declared canonical scope: REQUIREMENTS (with an acceptance-criteria status table), as-built ARCHITECTURE, REPORT (history and measurements), and one living HANDOFF; plus a START_HERE kickoff file and a task ledger that doubles as a delegation spec. Use on symptoms like "handoff docs keep going stale", "stale docs", "documentation restructuring", "living handoff", "onboarding a new agent onto an existing repository", "which document is the source of truth", dated handoff snapshots piling up, or 引き継ぎ資料の整理・要件定義書の逆起こし. Includes bilingual (EN/JA) templates.
claude-code-devlog-hooks
Dev-journal (devlog / 開発日誌) discipline for coding agents, enforced by three Claude Code hooks: SessionStart injects the routine, UserPromptSubmit nudges when today's log goes stale, Stop blocks turn-end once until today's journal is updated. Use when a session log / daily dev journal must be kept "little and often", when a Stop hook block message asks for today's journal entry, when a dev-journal nudge appears mid-session, or when setting up or debugging journaling hooks (enforce-once markers, fail-open, UTF-8 output). Keywords: dev journal, devlog, dev diary, 開発日誌, 開発ログ, session log, daily log, Stop hook block, journaling discipline.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.