pixelastic
58 verified skills2,204 total stars
zsh-writer
Use when writing or modifying ZSH functions.
documentation38
skill-writer
Use when creating or updating a discipline-enforcing skill.
testing38
glossary
Use when the user wants to nail down domain terms, resolve terminology ambiguities, or build a shared language for a module or repo. Drills vocabulary one question at a time and writes to the project GLOSSARY.md.
development38
code-writer
Use when writing or modifying code in any programming language. Apply when adding functions, fixing bugs, or implementing features.
development38
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
tools38
cfp-writer
Crafts compelling conference CFP submissions (title, abstract, takeaways). Use when user needs to write a Call for Paper, submit a talk proposal, or transform existing content into conference-ready format.
development38
code-writer
Use when writing or modifying code in any programming language. Apply when adding functions, fixing bugs, or implementing features.
development38
handoff
Compact the current conversation into a handoff document for another agent to pick up.
documentation38
grill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
testing38
slack-writer
Use when user needs to write Slack announcement messages but struggles with tone, length, or call-to-action. Triggers include 'help me write a Slack message', sharing personal projects, announcing meetups/events, or posting article links.
testing38
zsh-writer
Use when writing or modifying ZSH functions.
documentation38
to-issues
Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
tools38
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
testing38
js-writer
Use when writing or modifying JavaScript code. Apply when adding functions, fixing bugs, or implementing features.
development38
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
development38
handoff
Compact the current conversation into a handoff document for another agent to pick up.
documentation38
tdd
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.
development38
js-writer
Use when writing or modifying JavaScript code. Apply when adding functions, fixing bugs, or implementing features.
development38
slack-writer
Use when user needs to write Slack announcement messages but struggles with tone, length, or call-to-action. Triggers include 'help me write a Slack message', sharing personal projects, announcing meetups/events, or posting article links.
testing38
to-issues
Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
tools38
commit-writer
Use when the user needs a git commit message for staged changes.
documentation38
slack-writer
Use when user needs to write Slack announcement messages but struggles with tone, length, or call-to-action. Triggers include 'help me write a Slack message', sharing personal projects, announcing meetups/events, or posting article links.
testing38
tdd
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.
development38
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
tools38
js-writer
Use when writing or modifying JavaScript code. Apply when adding functions, fixing bugs, or implementing features.
development38
cfp-writer
Crafts compelling conference CFP submissions (title, abstract, takeaways). Use when user needs to write a Call for Paper, submit a talk proposal, or transform existing content into conference-ready format.
development38
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.
development38
spec-writer
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
testing38
code-quality-and-commits
Conducts multi-axis code review. Use before committing any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
development38
incremental-implementation
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
development38
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
testing38
skill-writer
Use when creating or updating a discipline-enforcing skill.
testing38
config/ai/claude/claudecode/skills/git-commit-writer
--- name: git-commit-writer description: Use when the user needs help writing commit messages, wants to commit staged changes, has multiple unrelated changes they want to split into logical commits, or asks to create/generate git commits. --- # Git Commit Writer ## Overview This skill analyzes your staged git changes and generates high-quality but concise commit messages following the Conventional Commits format. It automatically detects when staged files represent multiple logical concerns a
development38
issues
Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
tools38
prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
tools38
tdd
Used when user wants to build features or fix bugs using TDD or red-green-refactor loop.
development38
sidequest
Use when user says "sidequest" or "handoff" — compact conversation context into a document for a fresh agent to pick up.
documentation38
zsh-writer
Use when writing or modifying ZSH functions.
documentation38
slack-message-writer
Use when user needs to write Slack announcement messages but struggles with tone, length, or call-to-action. Triggers include 'help me write a Slack message', sharing personal projects, announcing meetups/events, or posting article links.
testing38
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
testing38
ralph
Use when user says "ralph <dir>" or "ralph this". Implements the highest-priority issue from state.json in the given directory using TDD, updates docs, runs review in a subagent, fixes actionable feedback, then stops for user to commit. Argument is the directory containing state.json and GUIDANCE.md.
documentation38
review
Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X". Reviews changes along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match the originating issue/PRD?). Runs both axes as parallel sub-agents and reports them side by side.
development38
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
tools38
code-writer
Use when writing or modifying code in any programming language. Apply when adding functions, fixing bugs, or implementing features.
development38
grill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
testing38
commit-writer
Use when the user needs a git commit message for staged changes.
documentation38
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
testing38
grill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
testing38
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
tools38
skill-writer
Use when creating or updating a discipline-enforcing skill.
testing38
ralph
Use when user says "ralph <dir>" or "ralph this". Implements the highest-priority issue from prd.json in the given directory using TDD, updates docs, runs review in a subagent, fixes actionable feedback, then stops for user to commit. Argument is the directory containing prd.json and progress.md.
documentation38
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
development38
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
tools38
cfp-writer
Crafts compelling conference CFP submissions (title, abstract, takeaways). Use when user needs to write a Call for Paper, submit a talk proposal, or transform existing content into conference-ready format.
development38
handoff
Compact the current conversation into a handoff document for another agent to pick up.
documentation38
ralph
Use when user says "ralph <dir>" or "ralph this". Implements the highest-priority issue from issues.json in the given directory using TDD, updates docs, runs review in a subagent, fixes actionable feedback, then stops for user to commit. Argument is the directory containing issues.json and progress.md.
documentation38
to-issues
Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
tools38
to-prd
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
tools38