Refactoring
Code restructuring and optimization
clean-functions
by ertugrul-dmr
Use when writing, fixing, editing, or refactoring Python functions. Enforces Clean Code principles—maximum 3 arguments, single responsibility, no flag parameters.
fixture-boundary-skill-name-padded-to-sixty-four-characters-long
by daishiman
Boundaries
improve
by atrislabs
"Run one verified, scored improvement tick and write its receipt. Use when the user asks to improve, make this better, ship one thing, run a tick, or get smarter. atris improve alone shows metabolism vitals; use atris improve tick to ship work."
tidy
by atrislabs
"Workspace maintenance and knowledge hygiene. Finds stale docs, broken refs, abandoned tasks, ghost names, duplicate scorecards, and fixes them. Use when things feel messy or you want the system to clean itself up. Triggers on: tidy, clean up, maintenance, lint, health check, freshen up, prune."
commit
by tkersey
Create micro-commits (minimal incision) with at least one validation signal per commit. Use when requests say "split this into micro commits," "stage only the minimal change and commit," "keep commits tiny while checks pass," or when parallel workers/slices need isolated, reviewable commits.
fin
by tkersey
"Finalize GitHub PRs end-to-end: update branch/PR, monitor CI until green, squash-merge, and clean up local/remote state. Use when asked to $fin or to finish/land/merge/close a PR, watch checks or runs, squash-merge, delete the branch, and sync local state."
clean-comments
by ertugrul-dmr
Use when writing, fixing, editing, or reviewing Python comments and docstrings. Enforces Clean Code principles—no metadata, no redundancy, no commented-out code.
boy-scout
by ertugrul-dmr
Use when fixing, editing, changing, debugging, or working with any Python code. Applies the Boy Scout Rule—always leave code cleaner than you found it. Orchestrates other clean code skills as needed.
python-clean-code
by ertugrul-dmr
Use when writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.
sound-design-film
by guia-matthieu
"Apply Walter Murch's legendary film sound principles to marketing video, creating emotionally resonant audio that audiences feel without consciously noticing. Use when: Designing sound for brand films and documentaries; Creating emotional impact in video ads; Layering music, effects, and voice effectively; Building immersive soundscapes for content; Elevating production value through audio"
postgis-knowledge-patch
by Nevaberry
This skill should be used when writing PostGIS queries, using spatial functions, geography types, raster operations, topology, or any PostGIS features from 3.5+ (2024-2026).
reflect
by JochenYang
Review current conversation, analyze tasks, errors, and user feedback, extract learning opportunities for skill improvement
tdd-workflow
by JochenYang
Standardized Test-Driven Development (TDD) cycle (RED-GREEN-REFACTOR-VERIFY). Use this skill to ensure code quality, high coverage, and regression prevention.
thinking-in-bets
by pmprompt
Use when asked to "thinking in bets", "make decisions under uncertainty", "think probabilistically", "avoid resulting", "separate decision quality from outcomes", or "reduce bias in decisions". Helps make explicit bets and evaluate decisions on process, not results. The Thinking in Bets framework (from Annie Duke) applies poker strategy to business and life decisions.
prompt-optimize
by YYH211
Expert prompt engineering skill that transforms Claude into "Alpha-Prompt" - a master prompt engineer who collaboratively crafts high-quality prompts through flexible dialogue. Activates when user asks to "optimize prompt", "improve system instruction", "enhance AI instruction", or mentions prompt engineering tasks.
data-sleuth
by petekp
Identify non-obvious signals, hidden patterns, and clever correlations in datasets using investigative data analysis techniques. Use when analyzing social media exports, user data, behavioral datasets, or any structured data where deeper insights are desired. Pairs with personality-profiler for enhanced signal extraction. Triggers on requests like "what patterns do you see", "find hidden signals", "correlate these datasets", "what am I missing in this data", "analyze across datasets", "find non-obvious insights", or when users want to go beyond surface-level analysis. Also use proactively when you notice interesting anomalies or correlations during any data analysis task.
review-clean-code
by Heyvhuang
'Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user requests code quality checks, refactoring advice, Clean Code analysis, code smell detection, or mentions terms like code review, code quality, refactoring check.'
review-clean-code
by Heyvhuang
'Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user requests code quality checks, refactoring advice, Clean Code analysis, code smell detection, or mentions terms like code review, code quality, refactoring check.'
skill-improver
by Heyvhuang
"Improve skills and workflows by analyzing run artifacts and execution logs (events.jsonl/state.json) under runs/ (or OpenSpec changes/). Use when you want to iterate on skills based on real runs: find failure modes, bottlenecks, unclear prompts, missing I/O contracts, and propose concrete edits."
scrum-sage
by michalparkola
AI-powered Scrum Master and Enterprise Agility Coach based on Jeff Sutherland, Taiichi Ohno, and First Principles thinking. Use when user needs help with Scrum, sprint analysis, backlog refinement, scaling advice, impediment removal, team dynamics, or agile coaching. Activate for questions about Scrum mechanics, Scrum@Scale, flow optimization, or team performance.
tdd
by brianlovin
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
simplify
by brianlovin
Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
build
by ZachArticulateV
"Implement planned work with proof at every step: execute a plan or tickets unit by unit, running independent units in parallel; refine code just written; or improve a measured metric, keeping only the wins that clear the noise. Use when the user asks to implement, build, execute a plan or ticket, clean up freshly written code, or make something faster or smaller."
reflection
by davidkiss
"Analyzes the conversation and tool usage to propose improvements to skills or store user preferences."