القائمة
Create well-formatted git commits using Conventional Commits format. Use when committing changes, reviewing commit messages, or splitting changes into atomic commits.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use bearcli to safely read, search, edit, tag, archive, and organize Bear.app notes. Use when working with Bear notes, note IDs, Bear tags, migrations from Obsidian, note cleanup, or personal knowledge management in Bear.
Use rn-logs to read React Native Metro logs via CDP without MCP overhead. Default output is plain text and safe for non-interactive agent runs.
Automate iOS Simulator using AXe CLI. Use after implementing features to verify they work correctly via UI automation.
Review code changes for quality, security, performance, and maintainability. Use when reviewing PRs, diffs, or code files. Provides structured feedback with severity levels.
Fetch source code for npm packages, Python packages, Rust crates, or GitHub repos to understand their implementation. Use when you need to explore a library's internals.
This skill should be used when users need to interact with GitHub via the gh CLI. It covers repository management (create, delete, clone, fork), CI/CD workflows (GitHub Actions), Issues, Pull Requests, Releases, and other GitHub operations. Triggers on requests mentioning GitHub, repos, PRs, issues, actions, or workflows.
| name | conventional-commit |
| description | Create well-formatted git commits using Conventional Commits format. Use when committing changes, reviewing commit messages, or splitting changes into atomic commits. |
Create atomic, well-formatted commits following the Conventional Commits spec.
type(scope): description
| Type | When to use |
|---|---|
feat | New feature |
fix | Bug fix |
refactor | Code change (no new feature/fix) |
docs | Documentation only |
style | Formatting, whitespace |
test | Adding/updating tests |
chore | Maintenance, dependencies |
perf | Performance improvement |
ci | CI/CD changes |
Optional. Derive from primary directory/module changed.
Examples: auth, api, ui, build, deps
Split changes if they touch:
Each commit should be independently revertable.
Good:
feat(auth): add JWT refresh token rotation
fix(api): handle null response in user endpoint
refactor: extract validation logic to shared util
chore: update dependencies
docs(readme): add setup instructions
Bad:
updated stuff # vague
Fixed the bug in the authentication # past tense, too long
WIP # meaningless
feat: add login and fix signup and update deps # not atomic
For breaking changes, add ! after type/scope:
feat(api)!: change response format for user endpoint
Or add BREAKING CHANGE: in commit body.