Menü
Use when committing staged changes with a Conventional Commit.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Configure clangd language server for Zephyr RTOS projects with cross-compilation toolchains. Use when setting up clangd for Zephyr, nRF Connect SDK, or ARM cross-compilation projects, or when clangd shows errors like "Unknown Arm architecture profile" or "failed to resolve include".
Use when debugging embedded firmware through SEGGER J-Link RTT - capture RTT output, send RTT console commands, or open an interactive RTT console.
Use for MCU firmware debugging with GDB/gdbserver, probe or QEMU targets, flash/attach flows, and Cortex-M fault analysis.
Use for Linux C/C++ GDB crash, core dump, and hang debugging.
Use when starting any coding task with unclear requirements, vague feature requests, or ambiguous bug fixes - before writing implementation code. Triggers automatic domain inference (Embedded, Python, DevOps, Zephyr, etc.) and compiles rigorous Markdown prompts with reconnaissance, HITL clarification, TDD workflow, and selectively applied domain constraints.
| name | git_commit |
| description | Use when committing staged changes with a Conventional Commit. |
Use this skill when:
Do not use this skill when:
Run:
git diff --cached --name-only
If nothing is staged, stop and tell the user to stage files first.
Run:
git diff --cached --stat
git diff --cached
Read the diff to understand the intent of the change. Do not generate the message from file counts, line counts, or filenames alone.
Before committing, check whether the staged files belong to one coherent change.
Usually atomic:
Usually not atomic:
If the commit looks non-atomic, stop and tell the user to split it first unless they explicitly want one combined commit.
Use Conventional Commit format:
<type>(<scope>): <subject>
Scope is optional:
<type>: <subject>
Rules:
! and BREAKING CHANGE: footer only for real breaking changesCo-Authored-By, AI, or Agent attributionfix: 9 filesupdate file, modify code, or cleanup changesfeat: new user-facing behavior or capabilityfix: bug fix or correctness fixdocs: documentation onlystyle: formatting only, no behavior changerefactor: structural change without behavior changeperf: performance improvementtest: add or adjust testsbuild: build tooling or dependenciesci: CI workflow/config changeschore: maintenance that does not fit aboverevert: reverting an earlier commit<type>(<scope>)!: <subject>BREAKING CHANGE: footer only for real compatibility breaksFor a one-line commit:
git commit -m "<subject>"
For a commit with body:
git commit -m "<subject>" -m "<body>"
Do not open an editor. Do not ask interactive yes/no questions unless the user explicitly asked for a preview instead of a commit.
The message must reflect why the change exists.
Good:
fix(auth): handle missing refresh token
refactor(git_commit): remove interactive helper scripts
docs(git_commit): simplify commit workflow
Bad:
fix: 9 files
chore: update code
refactor: modify scripts
If the user says "commit it" or equivalent:
git commitIf the user asks for message only:
git commitBasierend auf der SOC-Berufsklassifikation
