personal-greeting
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
- License 许可
- MIT
- 最近更新
- 2026-05-15
- Stars
- ★ 13
- Forks
- 1
01 前言 Front Matter
- name
- personal-greeting
- title
- personal-greeting
- description
- Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
03 SKILL.md 正文
Instructions
This skill is installed at the personal scope. Its expected location on disk is:
~/.claude/skills/personal-greeting/SKILL.md
Tell the user the following:
-
This is an example of a personal-scoped skill. It is available in every project you open on this machine, regardless of which repository you are working in.
-
Personal skills live at
~/.claude/skills/. Each skill is a directory with aSKILL.mdfile inside. The directory name must match thenamefield in the frontmatter. -
Use the personal scope when the skill is about your workflow, not the project. Good candidates for personal skills:
- Your commit message style preferences
- Your preferred code review checklist
- Shortcuts for tools you use everywhere (explain-code, summarize-changes, etc.)
-
Use the project scope (
.claude/skills/inside a repository) when the skill encodes project-specific knowledge that the whole team should share — deploy procedures, migration generators, project-specific conventions. -
If both scopes have a skill with the same name, the personal scope wins. You can always override a project skill with your own personal version.
Do not ask the user any follow-up questions unless they ask one first.
04 同仓库更多 Skills
tag-version
Bump the package version and create an annotated git tag. Accepts a semantic version number (1.2.0) or a bump type (patch, minor, major). Does not push — use the publish skill to push. Use as part of a release workflow.
release
Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.
publish
Push the current branch and all tags to origin, then create a GitHub release using the latest tag and its CHANGELOG.md entry. Use after tag-version to complete a release.
changelog-entry
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
auto-format-on-edit
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
code-quality-audit
Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.