---
title: "chris-skills"
description: "Portable agent skills: commit message generation, guided code walkthroughs, plain-English change explanations, and pre-implementation planning."
canonical: https://agentpluginsdirectory.com/plugins/chris-skills
last-updated: 2026-09-25
---

# chris-skills
Portable agent skills: commit message generation, guided code walkthroughs, plain-English change explanations, and pre-implementation planning.
- Slug: chris-skills
- Publisher: Chris Gregori
- Repository: https://github.com/chrisgreg/agent-plugins
- Manifest: plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): documentation
- Skills: 4 (ai-commit, code-walkthrough, eli5, plan-build)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-10
- Repository last pushed: 2026-08-10
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/chris-skills
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What chris-skills does, in the publisher's words

A personal, portable collection of agent skills, packaged as an Agent Plugin. The plugin format is client-agnostic: any coding agent that supports the spec (or the underlying Agent Skills format) can use these skills, which makes them easy to sync across machines and share with others.

Each directory under skills/ is one skill. A skill is just a SKILL.md file: YAML frontmatter (name, description, optional allowed-tools and metadata) followed by the instructions the agent loads when the skill is activated.

Claude Code discovers personal skills in ~/.claude/skills/. Symlink the ones you want so they stay in sync with this repo:

- Create skills/ /SKILL.md with frontmatter:
- Write the instructions in the Markdown body. Keep it under ~500 lines; move bulky material into references/ or scripts/ inside the skill directory.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/chrisgreg/agent-plugins/HEAD/README.md

## Skills

- ai-commit: Generate consistent, well-formatted commit messages from staged git changes. Analyzes staged files and produces a commit message with appropriate prefix (feat:, fix:, chore:, typo:, refactor:, docs:, style:, test:, perf:). Designed to be called via `claude -p` for use in shell aliases.
- code-walkthrough: Produce a guided, step-by-step walkthrough of how a piece of code works. Use when the user asks to explain, walk through, or break down how something in the codebase works, a feature, a flow, a worker, a pipeline, an integration, or any cross-module behaviour. Traces execution from entry point thr…
- eli5: Explain a PR, feature, or code change in plain English, big picture first, then a breakdown that a smart non-expert could follow. No jargon without explanation. Use when someone is confused about what a change is trying to do and why.
- plan-build: Inspect a software ticket, problem, feature, bug, migration, refactor, or infrastructure task and produce a clear pre-implementation walkthrough before changing code. Use when the user asks to begin a ticket, plan a build, explain what will be implemented, talk through the work first, understand th…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.