skill

agent-skills

Open-source Codex skills library inspired by hamzafer/cursor-commands, with guardrail-first triggering for reliable workflow automation.

gologo13/agent-skillscommunitylistedunreviewed

Use skill

Set up

Skills are installed by placing their folder where your agent loads skills.

Download ZIP from GitHub Open the repository

The download comes from github.com/gologo13/agent-skills itself, not from our server, so what you get is exactly what its author published.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below.

README

synced Oct 23, 2026

Codex Skills

A curated collection of Codex global skills for common engineering workflows. These skills are packaged as 1 skill = 1 directory with strict SKILL.md front matter for reliable triggering.

What This Repository Provides

32 reusable skills for common engineering workflows
Guardrail-oriented descriptions to reduce accidental trigger
Cautious-mode wording for risky workflows (e.g., security review, git push)

Repository Structure

<repo-root>/
  <skill-name>/
    SKILL.md
  README.md

Quick Start

Clone this repository.
Copy each skill directory into your Codex global skills path (~/.codex/skills or your configured skills directory).
Restart Codex/CLI session so metadata is reloaded.

Example:

mkdir -p ~/.codex/skills
for d in ./*/; do cp -R "$d" ~/.codex/skills/; done

Skill List

skill-name	description
accessibility-audit	Perform comprehensive accessibility (a11y) audit of the current UI code to ensure compliance...; keywords: wcag, accessibility, review, test. Use only on explicit request; skip in routine implementation discussions.
add-documentation	Add comprehensive documentation for the current code/feature and format it according to the ...; keywords: api, architecture, error. Use only on explicit request; skip in routine implementation discussions.
add-error-handling	Implement comprehensive error handling for the current code to make it robust and resilient ...; keywords: error. Use only on explicit request; skip in routine implementation discussions.
address-github-pr-comments	Process outstanding reviewer feedback, apply required fixes, and draft clear responses for e...; keywords: pr, test, fix. Use only on explicit request; skip in routine implementation discussions.
clarify-task	Before doing ANY coding work on the task I describe:; keywords: architecture, error. Use only on explicit request; skip in routine implementation discussions.
code-review	Perform a thorough code review that verifies functionality, maintainability, and security be...; keywords: security, pr, performance, architecture. Use only on explicit request; skip in routine implementation discussions.
create-pr	Create a well-structured pull request with proper description, labels, and reviewers; keywords: pull-request, pr, unit-test, test. Use only on explicit request; skip in routine implementation discussions.
database-migration	Help create and manage database migrations, generating complete migration files following th...; keywords: migration, performance, review, test. Use only on explicit request; skip in routine implementation discussions.
debug-issue	Help debug the current issue in the code by walking through the debugging process systematic...; keywords: debug, test, error, fix. Use only on explicit request; skip in routine implementation discussions.
deslop	Check the diff against main, and remove all AI generated slop introduced in this branch; keywords: deslop. Use only on explicit request; skip in routine implementation discussions.
diagrams	Analyze the provided code, architecture, or concept and generate a clear, well-structured Me...; keywords: mermaid, diagram, git, api. Use only on explicit request; skip in routine implementation discussions.
docker-logs	Tail logs from Docker containers to check for errors and monitor application behavior; keywords: docker, error. Use only on explicit request; skip in routine implementation discussions.
fix-compile-errors	Analyze the compilation errors in the current codebase and provide fixes for them, making th...; keywords: error, compile, fix. Use only on explicit request; skip in routine implementation discussions.
fix-git-issues	Help resolve common Git problems and conflicts with step-by-step commands and explanations f...; keywords: git, commit, rebase, fix. Use only on explicit request; skip in routine implementation discussions.
generate-api-docs	Create comprehensive API documentation for the current endpoints formatted as OpenAPI/Swagge...; keywords: api, openapi, swagger, error. Use only on explicit request; skip in routine implementation discussions.
generate-pr-description	Create a comprehensive pull request description based on the changes in this branch and form...; keywords: pull-request, pr, test. Use only on explicit request; skip in routine implementation discussions.
git-commit	Create a short, focused commit message and commit staged changes; keywords: git, review, commit, fix. Use only on explicit request; skip in routine implementation discussions.
git-push	Push current branch to origin and sync with remote updates; keywords: git, rebase. Use only on explicit request; before execution, review diffs and list impact scope.
light-review-existing-diffs	Perform a quick quality pass on current diffs to surface risky areas, ensure polish, and fla...; keywords: debug, review, test, fix. Use only on explicit request; skip in routine implementation discussions.
lint-fix	Analyze the current file for linting issues and automatically fix them according to the proj...; keywords: lint, fix. Use only on explicit request; skip in routine implementation discussions.
lint-suite	Run project linters, apply fixes, and ensure the codebase meets formatting and style require...; keywords: lint, pr, refactor, commit. Use only on explicit request; skip in routine implementation discussions.
onboard-new-developer	Comprehensive onboarding process to get a new developer up and running quickly; keywords: git, pr, onboard, architecture. Use only on explicit request; skip in routine implementation discussions.
optimize-performance	Analyze the current code for performance bottlenecks and provide optimization recommendation...; keywords: api, performance. Use only on explicit request; skip in routine implementation discussions.
overview	Generate two Mermaid diagrams to overview the product; keywords: mermaid, diagram, api, architecture. Use only on explicit request; skip in routine implementation discussions.
refactor-code	Refactor the selected code to improve its quality while maintaining the same functionality, ...; keywords: performance, refactor, coverage, error. Use only on explicit request; skip in routine implementation discussions.
roadmap	Analyze the codebase and generate a visual roadmap of potential features and improvements; keywords: mermaid, diagram, performance, roadmap. Use only on explicit request; skip in routine implementation discussions.
run-all-tests-and-fix	Execute the full test suite and systematically fix any failures, ensuring code quality and f...; keywords: test, fix. Use only on explicit request; skip in routine implementation discussions.
security-audit	Comprehensive security review to identify and fix vulnerabilities in the codebase; keywords: security, review, fix. Use only on explicit request; before execution, review diffs and list impact scope.
security-review	Perform a comprehensive security review of the current code and provide specific remediation...; keywords: security, api, review, error. Use only on explicit request; before execution, review diffs and list impact scope.
setup-new-feature	Systematically set up a new feature from initial planning through to implementation structure; keywords: architecture. Use only on explicit request; skip in routine implementation discussions.
visualize	Use mermaid diagram to visualize the data lineage of the referenced code or project; keywords: mermaid, diagram. Use only on explicit request; skip in routine implementation discussions.
write-unit-tests	Create comprehensive unit tests for the current code and generate the test file with proper ...; keywords: coverage, unit-test, test, error. Use only on explicit request; skip in routine implementation discussions.

Design Notes

description is optimized for trigger precision, not marketing copy.
For dangerous operations, descriptions explicitly require pre-checks (diff review and impact scope).
Original command body content is preserved as much as possible under each SKILL.md.

License

MIT. See LICENSE.