Skill UI

A comprehensive guide to integrating Lokalise into Continuous Integration/Continuous Deployment (CI/CD) workflows using GitHub Actions. This setup automates the entire translation lifecycle: uploading source strings on code pushes, downloading the latest translations during builds, and running PR checks to ensure translation coverage across all required locales. It eliminates manual file management, keeping code, translations, and CI pipelines perfectly synchronized.

This guide provides a comprehensive local development environment setup for Internationalization (i18n) using Lokalise. It details configuring the project structure, implementing CLI scripts for synchronizing source strings (push) and translations (pull), setting up file watching for hot reloading, and generating mock translations for robust offline testing. Ideal for developers managing multi-language applications.

A comprehensive guide for setting up Continuous Integration and Continuous Deployment (CI/CD) workflows for Obsidian plugins using GitHub Actions. This setup automates critical tasks like build validation on every push, manifest consistency checks, version number bumping, and structured GitHub releases, ensuring robust and reliable plugin deployment lifecycles.

Guide for automating Pushbullet operations through Composio’s Pushbullet toolkit via Rube MCP, covering discovery, connection checks, execution flows, and schema-aware best practices for reliable workflows.

A workflow for orchestrating Pushover operations through Composio’s Rube MCP connectors, covering tool discovery, connection validation, schema-aware execution, and recommended API calls for reliable automation.

Guidelines for responding to code review feedback with technical rigor: read every comment, restate requirements, verify against the codebase, ask clarifying questions, push back when technically needed, and implement fixes one at a time with testing.

This comprehensive guide details how to configure a complete Continuous Integration and Continuous Deployment (CI/CD) pipeline for Replit applications using GitHub Actions. Learn to connect your GitHub repository, set up automated testing on pull requests, perform post-deployment health checks, and ensure reliable, automated deployment whenever code is pushed.

This skill guides the setup of a robust, multi-environment architecture for Supabase, ensuring complete data isolation between development, staging, and production projects. It covers best practices for managing separate environment-specific secrets, safe database migration promotion (db push), environment-aware client initialization, and implementing safeguards to prevent accidental cross-environment operations in production. Essential for scaling SaaS applications.

Guides developers through receiving and responding to code review feedback: read carefully, restate requirements, verify against the codebase, evaluate correctness, push back with technical reasoning if needed, and implement one verified fix at a time.

This skill simulates a senior engineer's final, deep audit of an entire codebase before committing or pushing to a remote repository. It systematically checks for junk files, dead code, security vulnerabilities (secrets, injection flaws), and performance bottlenecks (N+1 queries). Use this pre-flight check before any major release or public deployment to ensure maximum code quality and production readiness.

This tool provides bidirectional synchronization between Playwright end-to-end tests and TestRail test management. Users can import comprehensive test cases from TestRail to generate Playwright test files, push test execution results (pass/fail/skip) back to TestRail, create new test runs, and keep test coverage synchronized across both platforms. It manages the entire automated testing lifecycle.

This skill guides users on setting up automated code quality gates directly at the Git level. It covers best practices using frameworks like Husky, lint-staged, and pre-commit. Users can enforce linting, formatting, type-checking, and standardized commit message conventions (e.g., Conventional Commits) before code is committed or pushed, significantly improving code hygiene and development workflow consistency.