Code Style

JetBrains/intellij-community/.claude/skills/code-style

JetBrains· v1.0.0

codingResmi

Resmi Sağlayıcı Skill'iView repo

Code style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance.

Dosyalar1 dosya

SKILL.md27 satır

Loading editor…

Kurulum

Önerilen

Tek komut — ajanınız otomatik olarak devreye alır.

AI aracını seç

Kurulum komutunu görmek için yukarıdan bir AI aracı seçin.

veya

Manuel Kurulum

Daha fazla adım

Dosyayı indirin ve ajanınızın sistem istemine yapıştırın.

Skill detayları

Versiyonv1.0.0

YazarJetBrains

Kategoricoding

Skill IDJetBrains/intellij-community/.claude/skills/code-style

İlgili skill'ler

ActionsGuidelines for implementing IntelliJ actions (AnAction). Use those rules when you need to create or change an action in the intellij platform.ActionsGuidelines for implementing IntelliJ actions (AnAction). Use those rules when you need to create or change an action in the intellij platform.Code StyleCode style rules for IntelliJ codebase. Use when writing or reviewing code for style compliance.CommitsUse this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes such as IJ-MR trailers in a final separate paragraph.CommitsUse this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes such as IJ-MR trailers in a final separate paragraph.Compare Python TypecheckersRun a Python file or snippet through the real third-party type checkers (ty, pyrefly, basedpyright, mypy, zuban) via uvx and collate their output into one Markdown report. Use when evaluating how a type should be inferred, debugging PyCharm code-insight / type-engine behaviour, or checking where the external checkers agree or disagree on a snippet.