skills.rest
JetBrains
JetBrainsOFFICIAL
Explore all skills by this author →
Website𝕏@jetbrainsGitHub

commits

Enforce YouTrack ticket and subsystem commit message formats in IntelliJ repositories.

20.4k|6.0k|Updated Sep 30, 2011
Search Tags:#git#workflow#commit#merge#conventional-commit#youtrack
One-click install
npx skills add https://github.com/JetBrains/intellij-community --skill commits-jetbrains
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commits
Source: https://github.com/JetBrains/intellij-community/tree/main/.agents/skills/commits
Command: npx skills add https://github.com/JetBrains/intellij-community --skill commits-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized guideline for commit messages in the IntelliJ repository, ensuring every production and non-production change includes a YouTrack ticket and a subsystem context to facilitate code reviews and traceability.

Core Features & Use Cases

  • Required Format: Production changes must follow "<YouTrack ticket ID> <subsystem>: <subject>" and non-production changes must use a label like "cleanup" or "docs" before the subsystem, ensuring clear categorization.
  • Use Case: When pushing a bug fix, include the YouTrack ticket (e.g., IDEA-125730) and the affected subsystem (e.g., editor: fix issue) to guarantee traceability and automated checks.
  • Guardrails: Enforces Safe Push principles and prevents unsafe commit patterns to reduce wasted CI cycles.

Quick Start

Always format commits with a YouTrack ticket and subsystem, e.g., IJPL-12345 editor: fix bug.

Frequently Asked Questions about commits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format a commit message with a YouTrack ticket for IntelliJ?▼

A valid IntelliJ commit message requires a YouTrack ticket and subsystem, formatted as "IDEA-125730 editor: fix issue". This ensures traceability and passes automated checks for production changes.

What is the required commit format for non-production changes in IntelliJ?▼

Non-production IntelliJ commit messages require a label like "cleanup" or "docs" before the subsystem. This categorization ensures clear context alongside the mandatory YouTrack ticket.

Does IntelliJ support WIP or squash prefixes for daily development commits?▼

IntelliV commit guidelines disallow WIP or squash/amend prefixes. Enforcing Safe Push principles prevents unsafe commit patterns, reduces wasted CI cycles, and maintains repository consistency.

Why does my IntelliJ commit fail Safe Push validation?▼

Your commit fails Safe Push validation if it lacks a YouTrack ticket, misses a subsystem, or uses disallowed WIP prefixes. Safe Push rules enforce standardized commit messages to reduce wasted CI cycles.

Can I use conventional commit messages instead of YouTrack tickets in the IntelliJ repository?▼

The IntelliJ repository requires a YouTrack ticket and subsystem context rather than conventional commit formats. This specific format facilitates code reviews and guarantees traceability across production and non-production changes.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
u9401066u9401066

git-pusher

Automate Git commit, push, and CI workflow triggering with pre-push validation.

Community
Intermediate
JetBrainsJetBrains
302

managing-youtrack

Automate YouTrack issue lifecycle management via REST API.

Official
Intermediate
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate