home/categories/automation-tools
category focus

Automation Tools

Script and automate repetitive tasks and workflows.

4208 스킬all categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
automation-tools
77

quality-check

Quality checks to run after every code change. Automatically triggered after code modifications to verify code quality and comment standards.

nokonoko1203
nokonoko1203
tools
open
automation-tools
77

code-review

Perform a thorough code review of pull requests following established guidelines, focusing on code quality, best practices, and maintainability while providing constructive feedback. Use when reviewing PRs or code changes.

nokonoko1203
nokonoko1203
tools
open
automation-tools
75

mach-project-overview

Overview of the `mach` compiler repository, build lifecycle, dependency rules, and workspace guidance for contributors.

octalide
octalide
tools
open
automation-tools
73

code-quality-gate

Automated code quality checks before commits. Use before committing code, when finishing a feature, or when user mentions "ready to commit" or "quality check".

Afaneor
Afaneor
tools
open
automation-tools
70

config-validator

Validate AIWG configuration files and project setup for correctness and completeness. Use when relevant to the task.

jmagly
jmagly
tools
open
automation-tools
70

commit

Generate and execute git commits following conventional commit format. Use when the user wants to commit changes, create a commit, or says "/commit". Analyzes staged/unstaged changes and creates properly formatted commit messages with type, optional scope, and descriptive subject.

vichannnnn
vichannnnn
tools
open
automation-tools
70

repo-analyzer

Analyze GitHub repositories for structure, documentation, dependencies, and contribution patterns. Use for codebase understanding and health assessment.

jmagly
jmagly
tools
open
automation-tools
69

template-ts-node

This skill should be used when the user asks to "create a TypeScript project", "set up Node.js project", "scaffold new project", "initialize TypeScript repo", "create a new library", "set up a CLI tool", or mentions setting up a new TypeScript/Node.js codebase.

PaulRBerg
PaulRBerg
tools
open
automation-tools
69

gh-cli

This skill should be used when the user mentions "gh CLI", "gh command", asks to "view repository info", "trigger workflows", "search GitHub", "manage codespaces", "check PR status", "list issues", or asks about GitHub CLI usage and automation from the command line.

PaulRBerg
PaulRBerg
tools
open
automation-tools
69

code-review

This skill should be used when the user asks to "review code", "review PR", "code review", "audit code", "check for bugs", "security review", "review my changes", "find issues in this code", "review the diff", or asks for pull request review or code audit.

PaulRBerg
PaulRBerg
tools
open
automation-tools
69

ls-lint

This skill should be used when the user asks to "configure ls-lint", "set up filename linting", "enforce naming conventions", "create .ls-lint.yml", "lint file names", "lint directory names", "file naming rules", "directory structure linting", or mentions ls-lint, directory naming rules, or filename conventions.

PaulRBerg
PaulRBerg
tools
open
automation-tools
69

biome-js

This skill should be used when the user asks to "configure Biome", "extend biome config", "set up BiomeJS", "add biome overrides", "biome lint-staged", "fix biome errors", or mentions biome.jsonc, Biome linting, or Biome formatting configuration.

PaulRBerg
PaulRBerg
tools
open
automation-tools
69

dry-refactor

This skill should be used when the user asks to "refactor duplicate code", "apply DRY principles", "eliminate code repetition", "extract common functionality", or mentions code duplication, similar patterns, repeated logic, or reusable abstractions.

PaulRBerg
PaulRBerg
tools
open
automation-tools
69

typescript

This skill should be used when the user asks to "configure TypeScript", "fix type errors", "use dayjs", "add type definitions", "set up React with TypeScript", mentions ".ts" or ".tsx" files, or asks about TypeScript best practices or TypeScript-specific tooling.

PaulRBerg
PaulRBerg
tools
open
automation-tools
67

big-review

Run ~/code/dotfiles/bin/review.sh to perform a multi-model review, evaluate findings, fix valid issues (with tests when possible), add clarifying comments for invalid findings, then run required checks. Use before PR creation or when the user asks for a deep review.

transloadit
transloadit
tools
open
automation-tools
66

makefile-for-telegram

Generate a Makefile for Telegram bot projects with LaunchAgent service management. Use when setting up a new Telegram bot project or adding service management to an existing one.

htlin222
htlin222
tools
open
automation-tools
66

rename-global-variable-or-function

Renaming a global variable or function requires additional steps in decompilation projects or the build will fail. Use this skill when you want to rename a global variable or function.

cdlewis
cdlewis
tools
open
automation-tools
66

legacy

Modernize legacy codebases, migrate frameworks, and reduce technical debt. Use for legacy system updates or framework migrations.

htlin222
htlin222
tools
open
automation-tools
66

refactor

Refactor code for quality, reduce technical debt, and improve maintainability. Use for cleanup tasks and code improvements.

htlin222
htlin222
tools
open
automation-tools
66

rename-a-c-file-or-header-file

Renaming a C file or associated header (.h) file requires additional steps in decompilation projects or the build will fail. Use this skill when you want to rename a C file and/or a header file.

cdlewis
cdlewis
tools
open
automation-tools
65

move-a-file

Move or rename a file while automatically updating all references in source code and documentation

Synthesys-Lab
Synthesys-Lab
tools
open
automation-tools
63

analyze-changes

Interactive chunk-by-chunk review of PR or branch changes. Identifies logical groupings, explains each chunk, and critiques for issues. Use when user says "analyze-changes", "review changes", "review this PR", "what changed", or "walk me through these changes".

kaushikgopal
kaushikgopal
tools
open
Previous
Page 53 / 176
Next