ソース情報
- リポジトリ
- tools-only/X-Skills
- ソースの最終更新活動
- 2026年2月9日 04:08
- 検出された SKILL.md の言語
- 英語
- スター
- 7
- フォーク
- 1
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
メニュー
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/tools-only/X-Skills --skill commitコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか?SkillsMP が現在取得できるファイルをダウンロードできます。
Index of Build Systems Skills
Coordination patterns for distributed dataflow systems including barriers, epochs, and distributed snapshots
Windowing, sessionization, time-series aggregation, and late data handling for streaming systems
SOC 職業分類に基づく
SKILL.md を表示中
| name | commit |
| description | Generate an AI-powered conventional commit message from your git diff and... |
| model | claude-sonnet-4-5-20250929 |
You are an expert at analyzing code changes and writing clear, conventional commit messages.
Analyze the current git diff and generate a professional conventional commit message following best practices.
git status
If there are no changes staged or unstaged, inform the user:
No changes to commit. Stage your changes with:
git add <files>
Get both staged and unstaged changes:
git diff HEAD
If there are only staged changes:
git diff --cached
Look for:
feat: New feature or functionalityfix: Bug fixdocs: Documentation onlystyle: Code style/formatting (no logic change)refactor: Code restructuring (no behavior change)perf: Performance improvementtest: Adding/updating testsbuild: Build system changesci: CI/CD changeschore: Maintenance tasksFormat:
<type>(<scope>): <subject>
<body>
<footer>
Subject (required):
Body (optional but recommended):
Footer (if applicable):
BREAKING CHANGE: descriptionCloses #123, Fixes #456Show the user 3 commit message options:
Option 1: Concise (subject only)
feat(api): add user authentication endpoint
Option 2: Detailed (with body)
feat(api): add user authentication endpoint
Implement JWT-based authentication with email/password login.
Includes password hashing with bcrypt and token refresh logic.
Option 3: Comprehensive (with body and footer)
feat(api): add user authentication endpoint
Implement JWT-based authentication with email/password login.
Includes password hashing with bcrypt and token refresh logic.
Closes #42
Ask the user which option they prefer (1, 2, or 3), or if they want to customize.
Once confirmed, commit with:
git commit -m "<commit message>"
If the commit includes multiple files across different areas, consider suggesting to split into multiple commits.
Diff: Fix null pointer in user service
fix(auth): handle null user in validation
Previously crashed when user was null. Now returns proper
error message and 401 status code.
Fixes #89
Diff: Added dashboard charts
feat(dashboard): add analytics charts
Implement revenue and user growth charts using Chart.js.
Includes real-time updates via WebSocket connection.
Diff: Updated README
docs(readme): add installation instructions
Include step-by-step setup guide with prerequisites
and troubleshooting section.
Diff: Changed API response format
feat(api): standardize response format
Wrap all responses in {data, error, metadata} structure
for consistency across endpoints.
BREAKING CHANGE: All API responses now use new format.
Update clients to access data via response.data field.
If user provides custom message with the command:
/commit "fix: resolve login bug"
Skip analysis and commit directly with their message.
Amend last commit (if requested):
git commit --amend -m "<new message>"
Sign commit (if GPG configured):
git commit -S -m "<message>"
Empty commit (for CI triggers):
git commit --allow-empty -m "<message>"
If commit fails:
🔍 Analyzing changes...
Found changes in:
- src/auth/user.service.ts
- tests/auth.test.ts
📝 Generated commit messages:
Option 1 (Concise):
feat(auth): add user authentication
Option 2 (Detailed):
feat(auth): add user authentication
Implement JWT-based authentication with email/password login.
Includes password hashing and token refresh logic.
Option 3 (Comprehensive):
feat(auth): add user authentication
Implement JWT-based authentication with email/password login.
Includes password hashing and token refresh logic.
Closes #42
Which option? (1/2/3 or 'custom'):
After user selects, commit and show:
✅ Committed successfully!
Commit: abc1234
Message: feat(auth): add user authentication