القائمة
Suggest conventional commit messages from diff and context. Use when committing changes, writing commit message, or summarizing staged changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Set up Jazz as a GitHub Action for automated PR code review and on-demand /jazz PR assistance. Use when the user asks to add Jazz to CI, create a GitHub Action workflow, set up PR review automation, enable /jazz commands on PRs, or integrate Jazz with GitHub. Triggers on "github action", "github actions", "ci", "pr review", "pr assistant", "jazz in ci", "/jazz".
Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.
Use the official Obsidian CLI (v1.12+) to manage vaults, notes, daily notes, search, tasks, tags, properties, links, templates, sync, publish, and workspaces. Use when the user mentions Obsidian, vaults, notes, or wants to automate note-taking and knowledge base workflows.
Help users create, manage, and refine custom personas for Jazz agents. Use when the user wants to define a new communication style, character, or identity for an agent.
Create new Jazz skills for automating workflows. Use when the user asks to create a skill, make a skill, or wants to define custom automation behavior.
Create and track task lists for complex multi-step work. Use when planning projects, breaking down work, tracking progress, or when a task has 3+ steps. Triggers on "plan", "todo", "task list", "break down", "step by step", or complex requests requiring multiple actions.
| name | commit-message |
| description | Suggest conventional commit messages from diff and context. Use when committing changes, writing commit message, or summarizing staged changes. |
Suggest clear, conventional commit messages from git diff, staged changes, and context.
git diff --staged (or git diff if nothing staged)<type>(<scope>): <short description>
[optional body]
[optional footer]
| Type | When to use |
|---|---|
| feat | New feature or capability |
| fix | Bug fix |
| docs | Documentation only |
| style | Formatting, whitespace, no logic change |
| refactor | Code change that isn't fix or feat |
| test | Adding or updating tests |
| chore | Build, tooling, deps, config |
| perf | Performance improvement |
auth, api, ui, clisrc/auth/ → scope authFrom diff that adds OAuth login:
feat(auth): add OAuth2 login
From diff that fixes null in user lookup:
fix(api): handle null in user lookup
From diff that only touches README:
docs: update README installation steps
From diff that refactors store without changing behavior:
refactor(store): extract user selectors
From diff that upgrades deps:
chore(deps): upgrade react to 18.2
Use when:
feat(api): add pagination to list endpoint
BREAKING CHANGE: list endpoint now returns { items, nextCursor } instead of a plain array.
Fixes #123 or Closes #123 for issuesBreaking change: ... for breaking changes# Staged changes (preferred)
git diff --staged --stat
git diff --staged
# Unstaged if nothing staged
git diff --stat
git diff
# Recent commits for style
git log -3 --oneline
Infer type and scope from:
src/auth/, docs/)test or mention in bodyIf staged changes mix multiple concerns: