slice-generator
Generate FSD-compliant slice boilerplate with pattern matching
Script and automate repetitive tasks and workflows.
Generate FSD-compliant slice boilerplate with pattern matching
Handle ESM/CJS module interoperability in the Orient monorepo. Use when encountering import errors, circular dependencies, module resolution issues, or "does not provide an export named" errors. Covers import patterns, re-export strategies, and avoiding circular dependency chains.
Review changed files, commit, and push to remote
Creates complete OpenCode folder structures with configuration files, agents, and commands
Sync dotfiles repository (homesick) with security checks. Use when: (1) Syncing dotfiles changes, (2) Committing dotfiles, (3) Pushing changes, (4) Running security checks, (5) After any file changes in ~/.claude/ or dotfiles repo. Triggers: "sync dotfiles", "commit dotfiles", "push changes", "security check", "dotfiles sync", "homesick sync", after file modifications in ~/.claude/.
Says "Pfaa... da' cine v-a lucrat aici?" before refactoring, improving, or reviewing code
This skill should be used when the user is working with Go projects (go.mod, *.go files), asking about "Go patterns", "Go architecture", "services", "repositories", or mentions "Go development", "Go project", "Go handlers", "Go testing".
Install the file-review tool. Use when user needs to install file-review on a new machine or asks how to set it up.
When you need to run tasks, build projects, or understand the workspace graph using Nx. Use this for all build, lint, and test operations.
Instructions for managing releases using Changesets. Use this when the user wants to create a new release version or document changes.
Validate GDScript changes by refreshing Godot cache and checking diagnostics. Use after creating or editing GDScript files.
High-performance text search using ripgrep (rg). Replace for traditional grep/sed tools.
Move, rename, or delete GDScript files with their .uid files for Godot projects. Use when reorganizing code, renaming scripts, or removing unused GDScript files.
Find and document file locations in the codebase. Use this when you need to locate implementation files, tests, configurations, or any code artifacts by feature or topic. Works with Grep, Glob, and LS tools.
Troubleshoots pickme indexing issues including missing files, stale indexes, gitignore conflicts, and root coverage. Use when files are missing from pickme, index seems stale, or when debugging, troubleshooting, or investigating pickme behavior.
Systematically retrieve and address PR code review comments using make pr-comments. Enforces DDD architecture, code organization principles, and quality standards. Use when handling code review feedback, refactoring based on reviewer suggestions, or addressing PR comments.
Clean up and organize markdown files dumped at project root. Routes files to appropriate directories (memos/, docs/, devops/docs/) or deletes obsolete content. Follows project file organization guidelines from CLAUDE.md.
Guide for writing idiomatic, maintainable Makefiles following modern best practices. Enforces safety headers (SHELL, .SHELLFLAGS, .DELETE_ON_ERROR), self-documenting help, .PHONY declarations, modular includes. Triggers on "makefile", "Makefile", "make target", "make rule", "make pattern", "make help", "make template", ".mk file", "make include", "make variable", "make phony", "make dependency", "build system", "make clean", "make install", "make test", "make build", "make all", "make default", "task runner", "make automation", "GNU make", "make recipe", "make prerequisite". PROACTIVE: MUST invoke when writing ANY Makefile or *.mk file.