Skill UI

This skill generates commit messages strictly following Sentry's conventions and the Conventional Commit format. It mandates a structured commit message including a type, scope, subject, body (explaining what and why), and a footer for issue references. Use this whenever committing code changes to ensure a highly readable, traceable, and standardized version history.

Master advanced Git techniques, including interactive rebase, cherry-picking, and bisecting, to manage complex version control scenarios. This guide provides structured workflows for cleaning commit history before merging, recovering from accidental changes, and efficiently tracking down the source of bugs across diverging branches.

A comprehensive toolkit for implementing production-grade observability in Obsidian plugins. It provides structured logging with log levels and history, a robust metrics collector (supporting counters, gauges, and timers for performance tracking), and an error tracker with deduplication. Users can build a real-time debug panel to monitor plugin performance, diagnose issues, and set up comprehensive error reporting.

This skill automatically generates structured and user-friendly changelogs by analyzing the complete git commit history. It groups commits by time period (daily/weekly) and classifies changes into key categories (Features, Fixes, Docs, etc.), providing a concise summary of recent development activity for end-users. Ideal for answering 'what changed recently' or summarizing project updates.

This advanced prompt simulates a Senior Project Manager and DevOps specialist. It takes comprehensive feature artifacts (PRD, technical breakdowns, testing plans) and generates a structured, automated GitHub project plan. It enforces Agile best practices (Epic > Feature > Story > Enabler > Task) and includes templates for issue creation, dependency management, risk assessment, and Definition of Done, ensuring robust project tracking within GitHub.

This workflow guides developers through generating standardized, descriptive commit messages using the Conventional Commits specification. It provides a structured XML template (including type, scope, description, body, and footer) and integrates directly into the Git workflow, ensuring project history is clean, traceable, and machine-readable. Ideal for maintaining large, collaborative codebases.

Transforms repo structure and commit history into two actionable markdowns—an architecture summary and a narrative story—so analysts can trace system intent, data flow, and team evolution.

This bundle is designed to collect comprehensive diagnostics for CoreWeave clusters, including GPU node status, Kubernetes Pod logs, event history, and API connectivity. It aggregates critical cluster-level resource allocation and failure data into a single, actionable archive. Use it when preparing a support ticket to expedite the diagnosis of complex infrastructure issues like stuck pods, OOM errors, or resource bottlenecks.

This tool assists engineers in transforming vague work logs into structured, evidence-backed impact statements for professional documentation. It uniquely mines Copilot CLI session logs, git commits, and GitHub PRs to reconstruct forgotten work. It enforces a mandatory 'Action → Result → Evidence' impact contract, making it indispensable for preparing performance reviews, promotion packets, and self-assessments.

This skill analyzes the comprehensive commit history between two branches to generate a concise, objective, and highly structured Pull Request (PR) description. It automatically groups changes by domain, summarizing the purpose, technical notes, and user impact, ensuring consistency and minimizing manual documentation effort.

This skill analyzes raw git diffs or change descriptions to generate clear, story-driven commit messages. It strictly adheres to the Conventional Commits specification, ensuring that messages thoroughly explain *why* a change was made, not just *what* changed. It is ideal for writing meaningful commit history, preparing pull requests, or summarizing complex code changes for team collaboration.

This skill generates structured and standardized Git commit messages following the Conventional Commits specification. By analyzing code changes (via diff or status), it helps developers automatically create clear, actionable, and searchable commit history messages, ensuring consistency across the project.