Skill Claude CodeCodex needs its repo
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, feat, fix, refactor.
Automated AI dev environment setup CLI with curated Skills collection for Claude Code and other AI coding assistants.
This repository also configures its own agents. See what custom-skills tells them →
Skill Claude CodeCodex needs its repo
Format commit messages following conventional commits standard. Use when: writing commit messages, git commit, reviewing commit history. Keywords: commit, git, message, conventional, feat, fix, refactor.
Skill Claude CodeCodex needs its repo
A tool for generating usage documentation from project sources. It can create a complete feature reference and a shorter cheatsheet from commands, skills, agents, workflows, scripts, and standards.
Skill Claude CodeCodex needs its repo
A guide for organizing project documentation such as README files, architecture notes, API references, and deployment instructions. It covers what different kinds of projects should document.
Skill Claude CodeCodex needs its repo
A guide for designing consistent error codes for applications and APIs. An error code is a short identifier that tells developers what kind of failure occurred.
Skill Claude CodeCodex needs its repo
Derive BDD scenarios and TDD test skeletons from approved SDD specifications. ATDD acceptance test tables are optional output for specialized needs. Use when: spec is approved, starting BDD/TDD implementation, generating test structures. Keywords: forward derivation, spec to test, BDD generation, TDD skeleton, test…
Skill Claude CodeCodex needs its repo
A guide for managing Git branches and merges, including branch names and common team workflows. Git is a system for tracking code changes and combining work from different branches.
Skill Claude CodeCodex needs its repo
A guide for applying a development process such as TDD, BDD, or SDD. TDD means writing tests before the code; BDD describes expected behavior; SDD plans changes in specifications first.
Skill Claude CodeCodex needs its repo
Manage and guide developers through active development methodology workflows. Use when: TDD, BDD, SDD, ATDD, or custom methodology workflows are needed. Keywords: methodology, workflow, TDD, BDD, SDD, ATDD, phase, checkpoint, development process.
Skill Claude CodeCodex needs its repo
A guide for arranging project folders and files according to common practices for different programming languages and frameworks.
Skill Claude CodeCodex needs its repo
A guide for deciding how to improve existing code, including when to refactor it gradually or replace it with a rewrite. Refactoring changes code structure without changing what it is meant to do.
Skill Claude CodeCodex needs its repo
A guide for preparing software releases with semantic versioning and changelogs. Semantic versioning uses major, minor, and patch numbers to describe the kind of change in a release.
Skill Claude CodeCodex needs its repo
A guide for writing clear requirements, user stories, and feature specifications. A user story describes a need from a user's point of view and the reason it matters.
Skill Claude CodeCodex needs its repo
A guide for examining existing software and turning what it does into specification documents. Specification-driven development means writing an agreed description of a system before changing it.
Skill Claude CodeCodex needs its repo
A guide for planning software changes in specification documents before implementation. Spec-Driven Development means proposing, reviewing, implementing, verifying, and archiving a change in defined stages.
Skill Claude CodeCodex needs its repo
A skill for checking whether a feature's tests cover eight areas, such as normal behavior, limits, errors, permissions, state changes, validation, integration, and AI-generated tests.
Skill Claude CodeCodex needs its repo
A testing guide covering common testing levels, including unit, integration, system, and end-to-end testing. It also supports ISTQB and industry testing-pyramid approaches.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: