fetch-source
Fetch source code for npm packages, Python packages, Rust crates, or GitHub repos to understand their implementation. Use when you need to explore a library's internals.
Script and automate repetitive tasks and workflows.
Fetch source code for npm packages, Python packages, Rust crates, or GitHub repos to understand their implementation. Use when you need to explore a library's internals.
This skill should be used when developing or modifying dotfiles using chezmoi. Covers using .chezmoidata for configuration data and modify_ scripts (or run_onchange_after_ scripts for symlinked directories) for non-destructive file merging. Particularly useful when needing to configure application settings without overwriting user preferences.
This skill provides patterns for safe, systematic refactoring including extract, rename, move, and simplification operations with proper testing and rollback strategies.
Creates .NET file-based apps from single C# files. Use when building scripts, utilities, or small applications without project files.
Execute self-correcting validation workflow. Use when validation fails, tests fail, or build breaks.
Fix last few build errors aggressively, get clean build, commit everything, and prepare for ship in Leavn iOS app
Generate properly configured tsconfig.json files for TypeScript projects with appropriate compiler options for various project types. Triggers on "create tsconfig", "generate tsconfig.json", "typescript config for", "configure TypeScript".
Write or update repository devops scripts with this project's conventions. Use when creating or modifying shell scripts in scripts/ or packages/*/scripts.
Use when creating, editing, or fixing any database migration file. MANDATORY before touching any file in supabase/migrations/. Prevents the critical mistake of editing already-pushed migrations.
Use when setting up git pre-commit and pre-push hooks - provides simple shell script approach and pre-commit framework method, both calling justfile commands for DRY principle
Performs a code review of the current branch changes and creates a PR if the code passes review, otherwise provides a task list for improvements. Use when the user asks to review code and create a PR, or to check if code is ready for PR.
Repo workflow for markdowntown CLI development and scans.
Orchestrates the entire Code Refactoring process (Planning -> Execution -> Closing). Manages the workflow by invoking specialized sub-skills like code-refactoring-planning, tdd-refactoring, and tdd-audit. Used for (1) repaying technical debt (e.g., extracting logic from fat controllers), (2) improving architectural compliance (e.g., enforcing dependency rules), and (3) preparing legacy code for new features (e.g., decoupling).
Analyze and reorganize project file structures, identify dependencies, clean technical debt, and establish architectural patterns. Use when users need to: organize messy codebases, understand file dependencies and import chains, refactor folder hierarchies, identify unused files or circular dependencies, detect cross-file connections, or establish consistent naming conventions and module boundaries for any programming language project.
Guides systematic file refactoring following @j0kz/mcp-agents modular architecture pattern to maintain files under 300 LOC through constants/, helpers/, utils/ extraction with proven results from 2...
[52] EXECUTE. Three-stage refactoring workflow: (1) iterative research of refactor/modularization options, (2) plan + risk/edge-case analysis + Scope150 validation, then implement with tests after user confirmation, and (3) apply Scout105 cleanup protocol. Use when asked to refactor, modularize, or restructure code safely.
Use this skill when creating or modifying database schema, writing migrations, or updating docs/03_database.md. This ensures consistent naming conventions and proper documentation workflow.
Mac 系统垃圾文件扫描和清理工具。用于识别和清理 macOS 系统中的缓存文件、开发临时文件、重复文件和大文件。当用户需要释放磁盘空间、清理开发项目构建产物、查找重复文件或找出占用大量空间的文件时使用此 skill。
Systematic code refactoring skill that transforms complex, hard-to-understand code into clear, well-documented, maintainable code while preserving correctness. Use when users request "readable", "maintainable", or "clean" code, during code reviews flagging comprehension issues, for legacy code modernization, or in educational/onboarding contexts. Applies structured refactoring patterns with validation.