Analyze Changes

JetBrains/youtrackdb/.claude/skills/analyze-changes

analysisResmi

Resmi Sağlayıcı Skill'iView repo

Analyze git changes (branch, commit, or current branch) and produce a design-oriented markup document with Mermaid diagrams, query/usage examples, data walkthroughs, PR context, and impact assessment.

Dosyalar1 dosya

SKILL.md192 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

Kategorianalysis

Skill IDJetBrains/youtrackdb/.claude/skills/analyze-changes

İlgili skill'ler

Ai TellsReviews any draft for AI writing tells and produces a clean rewrite. Catches structural fingerprints (negative parallelism like "It's not X, it's Y", bullet-everything, Title Case headings, adjective triads), analysis fingerprints (superficial -ing clauses, passive voice, vague attribution, hedge stacking), and tone fingerprints (throat-clearing, closing phrases like "In conclusion"). Use this skill whenever the user asks to humanize, de-AI, edit, polish, or sanity-check writing, including phras Code ReviewReview code, test, and workflow-machinery changes across multiple dimensions using specialized agents with triage-based selection.Create PlanResearch the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.Create PresentationGenerate a PPTX presentation explaining code changes on the current branch, with matplotlib diagrams and dark theme slides.Edit DesignApply an edit to `design.md` or `design-mechanics.md` through the mutation discipline: apply → auto-review → iterate → present. Use this instead of directly Editing those files.Execute TracksExecute the implementation plan: autonomous plan review (Phase 2) on first invocation, then track-by-track execution (Phase A review + decomposition, Phase B implementation, Phase C code review). Use after /create-plan to implement the planned work.