work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKET_ID]" or similar phrases.
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKET_ID]" or similar phrases.
Review a Gitlab Merge Request. Use when the user says "review" or "code review" or asks to review pull requests, merge requests, or analyze branch changes before merging
Generate a morning MR status report. Use when the user says "morning report", "mr status", "what needs my attention", or similar morning standup queries.
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform comp...
Send prompts to ChatGPT Pro via Playwriter browser automation. Use for cross-validation, second opinions, or leveraging GPT-5.2 Pro's research-grade intelligence.
Test and automate TUI applications using tuistory (Playwright for terminals). PREFERRED over tmux-tui for most cases. Use when you need reliable TUI automation with proper wait conditions instead of sleep hacks...
Convert a spec/architecture document into a PRD JSON file optimized for Ralph agent. Use when you have a design doc and need to create implementable tasks.
Interact with TUI applications via tmux. Consider using tuistory skill instead for better synchronization (waitForText vs sleep). Use tmux-tui when you need visual debugging via tmux attach, or when Bun is unav...
Instructions for committing changes to config files in the home directory using the dotfiles bare git repo.
Guidance for initializing new projects. Use framework/package manager commands instead of manual scaffolding.
Conditionally installs GitHub Packages component library at latest version. Adds to package.json when user requests it.
Generates src/shared/EnvConsts.ts for type-safe environment variable access. Provides TypeScript interface and exports for accessing Vite environment variables throughout the application.
Generates vitest.config.ts for unit testing configuration. Configures Vitest with Vue, TypeScript support, coverage thresholds, and test environment settings.
Conditionally generates .env.standalone file for micro-frontend applications only. Enables running micro-frontends in standalone mode without single-spa launcher. Skipped for standalone applications.
Generates .env.local file for local development environment variables. Contains developer-specific configuration like API URLs, ports, and feature flags. Gitignored for security.
Generates TypeScript declaration files (shims-vue.d.ts, shims-svg.d.ts) to enable type-safe imports of Vue components and SVG files.
Generates Babel configuration for JavaScript transpilation in tests. Creates babel.config.js file.
Generates public/ directory with static assets including favicons, app icons, and site.webmanifest for Progressive Web App (PWA) support.
Determines which files and dependencies to generate based on application type (standalone vs micro-frontend). Controls conditional features.
Reads config.json and prompts user for application parameters. Merges configuration with defaults for project generation.
Generates initial view components with mandatory unit tests. Creates HomeView.vue, PageNotFoundView.vue, and their .spec.ts test files (4 files total).
Generates src/shared/constants/global.ts file containing application-wide constants used throughout the application.
Generates entrypoint.sh script for Docker container runtime environment variable injection. Replaces placeholder values in built assets with actual environment variables at container startup.
Provides Vue component structure templates for Composition API and Options API. Used when generating .vue components and views to match user's selected API pattern preference.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.