Loading...
Loading...
Found 1,868 Skills
Generate daily standup reports from git history, PRs, and a persistent work log. Use when the user says "daily", "standup", "what did I do yesterday", "generate my daily", "daily sync", or asks for a summary of recent work.
Use when starting feature work that needs isolation from current workspace - creates isolated git worktrees with Flutter project setup
Fixes GitHub issues with parallel analysis. Use to debug errors, resolve regressions, fix bugs, or triage issues.
Manage integrate Sentry with CI/CD pipelines. Use when setting up GitHub Actions, GitLab CI, or other CI systems with Sentry releases and source maps. Trigger with phrases like "sentry github actions", "sentry CI", "sentry pipeline", "automate sentry releases".
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
Save and organize target artifacts (documents, presentations, markdown, images, SVGs) to ~/projects/artifacts-viewer. Use when user wants to save or organize docs, PDFs, PPTs, markdown files, images (PNG, JPG, SVG), or any visual/document artifacts to a central viewer location. Also use to initialize git repo for artifacts-viewer and push to GitHub.
Creates Checkmk werks (changelog entries) from git commits
Retrieve GitHub user profile and repository information using the gh CLI tool. Use when the user asks about their GitHub profile, statistics, repositories, or wants to view their GitHub information. Examples: Show me my GitHub profile, What are my top repositories, Get my GitHub stats.
Use when starting feature work that requires isolation from the current workspace or before executing an implementation plan - Create isolated git worktrees through intelligent directory selection and security verification
When referencing files, format them as markdown links with line numbers using GitHub-style #L syntax.
Reviews staged git changes for code quality, maintainability, readability, and potential regressions. Verifies changes make sense in context, improve maintainability, enhance readability, and don't introduce side effects. Use when reviewing staged changes, examining git diffs, or when the user asks to review modifications before committing.
Git best practices including commit message conventions, interactive rebase, conflict resolution, and repository hygiene. Reference for all git operations.