القائمة
Generate Conventional Commits-compliant commit messages from staged changes or a description of work done.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | writing-commit-messages |
| description | Generate Conventional Commits-compliant commit messages from staged changes or a description of work done. |
Generate structured commit messages that follow the Conventional Commits specification from staged changes or a description of the work.
Examine the staged diff or provided description:
Choose the appropriate Conventional Commits type:
| Type | When to use |
|---|---|
feat | A new feature or capability |
fix | A bug fix |
docs | Documentation-only changes |
style | Formatting, whitespace, semicolons (no logic change) |
refactor | Code restructuring without behavior change |
test | Adding or updating tests |
chore | Build process, dependencies, tooling |
perf | Performance improvements |
ci | CI/CD configuration changes |
Identify a short scope token in parentheses:
auth, api, cli)Structure the commit message:
{type}({scope}): {description} — imperative mood, lowercase, no period, max 72 charactersCloses #123), note breaking changes (BREAKING CHANGE: ...){type}({scope}): {short description}
{Optional body explaining motivation and context}
{Optional footer with references or breaking change notes}
Single-line:
feat(api): add pagination to the list users endpoint
With body and footer:
fix(auth): prevent token refresh race condition
Two concurrent requests could both attempt to refresh an expired token,
causing one to fail with a 401. Added a mutex to serialize refresh calls.
Closes #42
feat!) and the footerSummarize git history, staged diffs, or PR changes into clear, human-readable summaries grouped by theme.
Build marketing-grade code displays for the Musher marketing site -- split-panel code-then-output layouts, CSS-only syntax highlighting, tabbed views, and terminal chrome. Use when implementing IA Section 3 (Mechanism), building code blocks, creating terminal demos, highlighting YAML/CLI output, or adding copy buttons to code. Triggered by: code display, code block, syntax highlighting, code-then-output, split panel code, terminal chrome, YAML highlight, CLI output, code snippet, tabbed code, multi-language code, mechanism section code, bundle yaml, pipeline yaml, marketing code.
Scaffold marketing page sections from IA definitions into Svelte 5 components. Use when building section components from the Information Architecture, translating archetypes to markup, mapping content slots to elements, or creating section scaffolds. Triggered by: scaffold section, build section, IA to component, section component, hero section, mechanism section, value grid, proof block, community block, CTA block, social proof bar, content slot, archetype component, layout pattern, section scaffold, marketing component.
Analyze CSV data by computing aggregations, filtering rows, and generating readable summaries. Use when working with tabular data files in a container environment where the agent creates and manipulates files directly.
Ensure local development environments match CI/CD environments for consistent behavior including shared version sources, devcontainer reuse in CI, reproducible dependency installation, environment variable parity, Docker image sharing, and lock file enforcement. Use when diagnosing works-on-my-machine issues, designing CI pipelines that mirror local dev, or auditing environment parity. Triggered by: CI alignment, CI environment, works on my machine, CI parity, environment parity, CI local match, GitHub Actions, CI pipeline, CI docker, reproducible builds, lock file, frozen lockfile.
Audit a repository for developer environment configuration completeness covering version pinning, editor config, task runner, env var documentation, setup scripts, devcontainer presence, Docker configuration, and CI alignment. Produces a gap analysis with maturity scoring and prioritized recommendations. Use when assessing a project's developer experience maturity, onboarding to a new codebase, or evaluating developer environment quality. Triggered by: environment audit, dev experience audit, DX audit, environment completeness, environment review, onboarding review, dev setup review, environment maturity, environment assessment, developer experience.