@jhongutang0116/claude-skills

Personal Claude Code skill library. Install the package once, run one command, and the skills land in a project's .claude/skills/ (or ~/.claude/skills/ for every project on the machine) — no hand-copying.

Bundled skills

| Skill | What it does | |---|---| | implementation-workflow | Build pipeline with two modes: a Lite path (one scope sign-off → build → verify) for small changes, and a Full path — gated SRS → Development → Testing → Documentation — for large or risky features. Stack-agnostic. | | plan-checklist | Generates and enforces a single plan.md that is both the build plan and the checklist. Owns per-turn discipline: work in order, check boxes only against verified work, log deviations. | | change-impact | Before editing existing code, maps callers, tests, and contracts (interfaces, schemas, public APIs, payloads) so a "small" edit doesn't regress something out of view. | | verification | A fast, honest self-review pass on one change before it's called done: re-read the real diff, walk each requirement to the line that satisfies it, actually run the tests/linters, clear leftovers, report honestly. | | debugging-assistant | Structured root-cause debugging — reproduce → isolate → hypothesise → test the hypothesis → fix the root → verify → prevent — instead of guess-and-check. | | pr-commit-writer | Turns an actual git diff into a commit message and PR description that match the repo's real conventions. |

Run npx claude-skills list to see what a given version ships.

Which skill when

| Situation | Skill | |---|---| | "Let's build / add / implement X" | implementation-workflow picks Lite vs Full | | Turning an approved spec into ordered tasks; "what's next", "mark that done" | plan-checklist | | About to change a signature, shared helper, data model, or public API | change-impact | | About to say "done" / check a box / "this should pass" | verification | | Something is broken, crashing, flaky, or a test fails | debugging-assistant | | Ready to commit or open a PR | pr-commit-writer |

They chain: implementation-workflow (Full) → plan-checklist runs throughout → change-impact + verification gate the risky and the finished work → pr-commit-writer at the end. Each also stands alone.

Install into another project

npm install -D @jhongutang0116/claude-skills
npx claude-skills install                        # all skills
npx claude-skills install implementation-workflow   # just one (or list several)

This copies each selected skill into ./.claude/skills/<name>/. Claude Code picks them up automatically as project skills. Run npx claude-skills list first to see the available names.

To keep them in sync on every npm install, add to that project's package.json:

{
  "scripts": {
    "postinstall": "claude-skills install --force"
  }
}

Then either commit .claude/skills/ or add it to that project's .gitignore and let postinstall regenerate it.

Install once for every project on the machine

npm install -g @jhongutang0116/claude-skills
claude-skills install --global      # -> ~/.claude/skills/

Re-run after upgrading the package (npm update -g @jhongutang0116/claude-skills).

Updating to a new version

Bumping the installed package does not touch the skill copies already sitting in .claude/skills/ — you have to re-run install (with --force) to refresh them.

Global install:

npm update -g @jhongutang0116/claude-skills
claude-skills install --global --force

Project install (-D):

npm update @jhongutang0116/claude-skills
npx claude-skills install --force

A project with the postinstall hook above refreshes itself on npm update — no second command needed.

Installed straight from GitHub (no npm publish):

npm install github:JhonGutang/personal-skill-library
npx claude-skills install --force

Then confirm what landed with npx claude-skills list.

Install without publishing to npm

Works straight from GitHub — no registry account needed, private repo is fine:

npm install -D github:JhonGutang/personal-skill-library
npx claude-skills install

CLI

claude-skills install [skill...] [--dir <path>] [--global] [--force] [--dry-run]
claude-skills list
claude-skills --help

• skill... — names to install; omit to install every bundled skill. An unknown name is rejected with the list of valid ones.
• --dir <path> — target project directory (default: current directory). Skills go into <path>/.claude/skills/.
• --global — target ~/.claude/skills/ instead of a project.
• --force — overwrite skills that already exist at the destination.
• --dry-run — print the plan without writing.

claude-skills install plan-checklist --dir ../other-project --force
claude-skills install implementation-workflow --global

Adding or editing a skill

1. Create skills/<skill-name>/SKILL.md with YAML frontmatter (name, description) plus any references/, assets/, scripts/ the skill needs.
2. node bin/cli.js list to confirm it's discovered (a directory counts as a skill only if it contains SKILL.md).
3. Bump the version and publish (below).

Publishing a new version

npm version patch        # or minor / major — commits + tags
npm publish              # publishConfig.access=public handles scoped visibility
git push --follow-tags

Publishing needs 2FA on the npm account: either run npm publish and enter the authenticator OTP when prompted (--otp=<code> to pass it inline), or publish with a granular access token that has "bypass 2FA" enabled (see ~/.npmrc setup below — required for CI).

# token-based auth (put in ~/.npmrc, never commit it):
//registry.npmjs.org/:_authToken=npm_xxxxxxxxxxxxxxxxxxxx

Local testing before publishing

npm pack                 # inspect the .tgz contents
npm link                 # then, in another project:
claude-skills install
npm rm -g @jhongutang0116/claude-skills