Skill
idea-analogist
想法群聊室 — 类比者角色。被 idea-team 主编排器调用，或用户单独说"类比一下"、"别的行业有没有"、"yes-and 扩展"、"X 让你想到什么"、"跨界启示"时触发。**专门做跨界类比 + yes-and 扩展——不评判、不挑刺、不要求事实证据**。Do NOT use when 用户要数据（用…
@majiayu000View SkillDevelopment
Skill
/git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
Install
$ npx -y skills add majiayu000/spellbook --skill git-commit-smart --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/git-commit-smart
Context preview
The summary Claude sees to decide when to auto-load this skill.
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
SKILL.md
git-commit-smart.SKILL.mdname: git-commit-smart
description: Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
Smart Git Commit
> Inspired by [claude-code-plugins-plus](https://github.com/jeremylongshore/claude-code-plugins-plus)
Purpose
Automatically generate meaningful commit messages by analyzing staged changes, following conventional commit format.
Commit Message Format
<type>(<scope>): <subject>
<body>
<footer>
Types
| Type | Description | |------|-------------| | `feat` | New feature | | `fix` | Bug fix | | `docs` | Documentation only | | `style` | Formatting, no code change | | `refactor` | Code change, no new feature or fix | | `perf` | Performance improvement | | `test` | Adding/updating tests | | `chore` | Maintenance tasks | | `ci` | CI/CD changes | | `build` | Build system changes |
Scope
Optional, indicates the section of codebase:
- `auth`, `api`, `ui`, `db`, `config`, etc.
Subject
- Imperative mood ("add" not "added")
- No period at end
- Max 50 characters
- Lowercase
Body
- Explain WHAT and WHY, not HOW
- Wrap at 72 characters
- Separate from subject with blank line
Footer
- Breaking changes: `BREAKING CHANGE: description`
- Issue references: `Closes #123`, `Fixes #456`
Workflow
1. Analyze Changes
# View staged changes
git diff --staged
# View changed files
git diff --staged --name-only
# View stats
git diff --staged --stat
2. Determine Type
Based on changes:
- New files with features → `feat`
- Modified files fixing issues → `fix`
- Only .md files → `docs`
- Only test files → `test`
- package.json, configs → `chore` or `build`
3. Identify Scope
Look at file paths:
- `src/auth/*` → scope: `auth`
- `src/api/*` → scope: `api`
- `tests/*` → scope: `test`
- Multiple areas → omit scope or use broader term
4. Write Subject
Summarize the change:
feat(auth): add OAuth2 login support
fix(api): handle null response in user endpoint
docs: update README with installation steps
refactor(db): extract query builder to separate module
5. Write Body (if needed)
For complex changes:
feat(auth): add OAuth2 login support
Implement OAuth2 authentication flow with support for
Google and GitHub providers. This allows users to sign
in without creating a separate account.
- Add OAuth2 client configuration
- Implement callback handlers
- Store OAuth tokens securely
- Add provider selection UI
Examples
Simple Feature
feat(ui): add dark mode toggle
Bug Fix with Issue Reference
fix(api): prevent duplicate user creation
Check for existing email before inserting new user record.
Race condition could cause duplicate entries when requests
arrived simultaneously.
Fixes #234
Breaking Change
feat(api)!: change response format to JSON:API
BREAKING CHANGE: All API responses now follow JSON:API
specification. Clients must update their parsers.
Migration guide: docs/migration-v2.md
Multiple Files, Single Purpose
refactor: extract validation logic to shared module
Move duplicate validation code from controllers to
a shared validation module. Reduces code duplication
and ensures consistent validation across endpoints.
Anti-Patterns to Avoid
❌ "fix stuff"
❌ "update code"
❌ "WIP"
❌ "changes"
❌ "fixed bug"
❌ "misc updates"
❌ Commits with 50+ files and vague message
Best Practices
1. **Atomic commits** - One logical change per commit 2. **Meaningful messages** - Future you will thank present you 3. **Reference issues** - Link to tickets/issues when relevant 4. **Review before commit** - `git diff --staged` always 5. **Don't commit secrets** - Check for API keys, passwords
Quick Reference
# Stage specific files
git add <file>
# Stage all changes
git add -A
# Interactive staging
git add -p
# Commit with message
git commit -m "type(scope): subject"
# Commit with body
git commit -m "type(scope): subject" -m "body paragraph"
# Amend last commit
git commit --amend
Read more
name: git-commit-smart description: Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
Smart Git Commit
> Inspired by [claude-code-plugins-plus](https://github.com/jeremylongshore/claude-code-plugins-plus)
Purpose
Automatically generate meaningful commit messages by analyzing staged changes, following conventional commit format.
Commit Message Format
<type>(<scope>): <subject> <body> <footer>
Types
| Type | Description | |------|-------------| | `feat` | New feature | | `fix` | Bug fix | | `docs` | Documentation only | | `style` | Formatting, no code change | | `refactor` | Code change, no new feature or fix | | `perf` | Performance improvement | | `test` | Adding/updating tests | | `chore` | Maintenance tasks | | `ci` | CI/CD changes | | `build` | Build system changes |
Scope
Optional, indicates the section of codebase:
- `auth`, `api`, `ui`, `db`, `config`, etc.
Subject
- Imperative mood ("add" not "added")
- No period at end
- Max 50 characters
- Lowercase
Body
- Explain WHAT and WHY, not HOW
- Wrap at 72 characters
- Separate from subject with blank line
Footer
- Breaking changes: `BREAKING CHANGE: description`
- Issue references: `Closes #123`, `Fixes #456`
Workflow
1. Analyze Changes
# View staged changes git diff --staged # View changed files git diff --staged --name-only # View stats git diff --staged --stat
2. Determine Type
Based on changes:
- New files with features → `feat`
- Modified files fixing issues → `fix`
- Only .md files → `docs`
- Only test files → `test`
- package.json, configs → `chore` or `build`
3. Identify Scope
Look at file paths:
- `src/auth/*` → scope: `auth`
- `src/api/*` → scope: `api`
- `tests/*` → scope: `test`
- Multiple areas → omit scope or use broader term
4. Write Subject
Summarize the change:
feat(auth): add OAuth2 login support fix(api): handle null response in user endpoint docs: update README with installation steps refactor(db): extract query builder to separate module
5. Write Body (if needed)
For complex changes:
feat(auth): add OAuth2 login support Implement OAuth2 authentication flow with support for Google and GitHub providers. This allows users to sign in without creating a separate account. - Add OAuth2 client configuration - Implement callback handlers - Store OAuth tokens securely - Add provider selection UI
Examples
Simple Feature
feat(ui): add dark mode toggle
Bug Fix with Issue Reference
fix(api): prevent duplicate user creation Check for existing email before inserting new user record. Race condition could cause duplicate entries when requests arrived simultaneously. Fixes #234
Breaking Change
feat(api)!: change response format to JSON:API BREAKING CHANGE: All API responses now follow JSON:API specification. Clients must update their parsers. Migration guide: docs/migration-v2.md
Multiple Files, Single Purpose
refactor: extract validation logic to shared module Move duplicate validation code from controllers to a shared validation module. Reduces code duplication and ensures consistent validation across endpoints.
Anti-Patterns to Avoid
❌ "fix stuff" ❌ "update code" ❌ "WIP" ❌ "changes" ❌ "fixed bug" ❌ "misc updates" ❌ Commits with 50+ files and vague message
Best Practices
1. **Atomic commits** - One logical change per commit 2. **Meaningful messages** - Future you will thank present you 3. **Reference issues** - Link to tickets/issues when relevant 4. **Review before commit** - `git diff --staged` always 5. **Don't commit secrets** - Check for API keys, passwords
Quick Reference
# Stage specific files git add <file> # Stage all changes git add -A # Interactive staging git add -p # Commit with message git commit -m "type(scope): subject" # Commit with body git commit -m "type(scope): subject" -m "body paragraph" # Amend last commit git commit --amend
Ships withmajiayu000-spellbook
Cross-runtime skills for Claude Code, Codex, and multi-agent workflows.
Get the whole plugin
Stats
277
Stars
26
Forks
Active
Maintenance
Python
Language
MIT
License
1d ago
Last commit
9mo ago
Created
Repo: majiayu000/spellbook
Other skills on majiayu000-spellbook.
@majiayu000View SkillSkill
idea-devils-advocate
想法群聊室 — 反方角色。被 idea-team 主编排器调用，或用户单独说"反方意见"、"挑这个想法的刺"、"为什么会失败"、"找漏洞 / 反例"、"devil's advocate"时触发。**专门挑漏洞、找隐藏假设、给反例——不安慰、不"也许可以这样"、不全盘否定**。Do NOT use when…
@majiayu000View SkillSkill
idea-research
想法群聊室 — 调研员角色。被 idea-team 主编排器调用，或用户单独说"调研一下 X"、"X 的现状/竞品/数据"、"找 2026 数据"、"事实底"时触发。**用 WebSearch 拉真实 2026 数据、列竞品、引来源——只给事实，不评判，不建议**。Do NOT use when…
@majiayu000View SkillSkill
idea-team
想法群聊室主持人 — 把一句话想法丢给多角色 AI 团队（调研员/反方/类比者）做查漏补缺。每个角色有自己的 voice，他们互相 @ 接话；你随时插话。**这是创意扩展工具，不打分、不否决、不堵路**。Use when 用户说"组个团队聊一下"、"开会讨论这个想法"、"找几个角度看看"、"群聊一下 X"、"team…
@majiayu000View SkillSkill
idea-to-product
端到端产品教练 — 把一句话想法走到 PRD + 可点击 HTML 原型。会顶嘴、强制砍功能、用 Nielsen + Norman 做友好性硬检。Use when user 说"我有一个想法"、"想做一个产品"、"做 MVP"、"写 PRD"、"做用户友好的产品"，或调用插件命令…
@majiayu000View SkillSkill
app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform…
@majiayu000View Skill