Skills

A collection of reusable development skills for Codex, Claude Code, and Gemini CLI.

Overview

This repository contains focused, self-contained skills for recurring engineering tasks. The current base is Android-oriented, with adjacent workflow skills for GitHub, CI, code simplification, and release preparation.

Available Skills

This repository currently includes:

Skill	Folder	Description
Android Compose Starter	android-compose-starter	It guides you through scaffolding a production-ready Android project from scratch and enforces modern architecture patterns, library choices, and Compose best practices throughout development.
Android Compose Review	android-compose-review	It reviews and incrementally improves an existing Android Jetpack Compose codebase using modern Compose patterns, migration guidance, and safe cleanup practices.
GitHub PR and CI	github-pr-and-ci	It uses the GitHub CLI to inspect pull requests, workflow runs, checks, CI failures, and structured GitHub API data.
Play Store Release Notes	play-store-release-notes	It generates Play Store release notes from git logs, PRs, commit history, changelogs, or release briefs, and differentiates the output for internal, beta, and production tracks.
Simplify Code	simplify-code	It reviews changed code for reuse, quality, efficiency, and clarity issues, then optionally applies only high-confidence, behavior-preserving simplifications.
Skill Template	skill-template	A reusable base for authoring new skills with a consistent structure: SKILL.md, README.md, and focused files in references/.

Usage

Each skill is self-contained. Refer to the SKILL.md file in each skill directory for triggers, workflow guidance, examples, and supporting references.

Setup

Skills are file-based. You can install this repository as a shared skill library and then expose the relevant folders to your CLI tool of choice.

The examples below assume the repository is available at:

git clone https://github.com/davideagostini/ai-dev-skills.git /tmp/skills

Adjust the destination folder if you want a different local clone path.

Claude Code

Claude Code loads skills from ~/.claude/skills/ for personal use across projects, or from .claude/skills/ inside a specific project.

Personal install:

# Clone the repository
git clone https://github.com/davideagostini/ai-dev-skills.git /tmp/skills

# Copy all skills into your personal Claude skills directory
mkdir -p ~/.claude/skills
cp -r /tmp/skills/* ~/.claude/skills/

Project-specific install:

# Clone the repository
git clone https://github.com/davideagostini/ai-dev-skills.git /tmp/skills

# Copy all skills into the current project's Claude skills directory
mkdir -p .claude/skills
cp -r /tmp/skills/* .claude/skills/

Claude Code discovers SKILL.md files automatically.

Codex CLI (OpenAI)

Codex reads local instructions from AGENTS.md. The simplest setup is to add this skills repository to your project and reference the skill folders you want Codex to use.

Add an AGENTS.md file to your project root:

# AGENTS.md

## Available Skills

The project includes reusable skills in `skills/`.

- For Android project scaffolding, follow `skills/android-compose-starter/SKILL.md`
- For review and modernization of an existing Compose codebase, follow `skills/android-compose-review/SKILL.md`
- For GitHub PR, Actions, and CI debugging, follow `skills/github-pr-and-ci/SKILL.md`
- For Play Store release notes, follow `skills/play-store-release-notes/SKILL.md`
- For change-focused cleanup and safe simplification, follow `skills/simplify-code/SKILL.md`

When a task matches one of these domains, consult that skill's `SKILL.md` first and load the relevant files from its `references/` directory as needed.

Add the repository to your project, for example as a submodule:

git submodule add https://github.com/davideagostini/ai-dev-skills.git skills

If you do not want a submodule, you can also copy the repository into your project as a normal folder and point AGENTS.md at the copied paths.

Gemini CLI (Google)

Gemini CLI reads project instructions from GEMINI.md. Add this repository to your project and point Gemini at the skill folders you want it to follow.

Add a GEMINI.md file to your project root:

# GEMINI.md

## Available Skills

This project includes reusable skills in `skills/`.

Use the matching skill for the task:

- Android scaffolding and Compose architecture:
  `skills/android-compose-starter/SKILL.md`
- Existing Compose codebase review and modernization:
  `skills/android-compose-review/SKILL.md`
- GitHub PR, Actions, and CI debugging:
  `skills/github-pr-and-ci/SKILL.md`
- Play Store release notes:
  `skills/play-store-release-notes/SKILL.md`
- Review and simplify changed code:
  `skills/simplify-code/SKILL.md`

Before answering, consult the selected skill's `SKILL.md` and then load the relevant files from its `references/` directory when deeper guidance is needed.

Add the repository to your project, for example as a submodule:

git submodule add https://github.com/davideagostini/ai-dev-skills.git skills

Verify the structure

Regardless of the tool, the repository should remain structured like this:

skills/
├── android-compose-starter/
│   ├── SKILL.md
│   └── references/
├── android-compose-review/
│   ├── SKILL.md
│   └── references/
├── github-pr-and-ci/
│   ├── SKILL.md
│   └── references/
├── play-store-release-notes/
│   ├── SKILL.md
│   └── references/
├── simplify-code/
│   ├── SKILL.md
│   └── references/
└── skill-template/
    ├── SKILL.md
    └── references/

Creating New Skills

Use skill-template/ as the default starting point for new skills. Copy it, rename the folder, update the frontmatter in SKILL.md, then replace the generic workflow and reference content with domain-specific guidance.

Contributing

New skills should stay focused, reusable, and consistent with the rest of the repository.

When adding a new skill:

• Give it one clear purpose instead of combining multiple unrelated jobs
• Write a concise but operational SKILL.md with workflow, output rules, and checklist
• Follow the same structure used by the existing skills
• Move detailed guidance into references/ instead of overloading the main skill file
• Add examples that make the intended usage obvious
• Update this root README so the new skill appears in the catalog and setup guidance when relevant

As a rule of thumb, a good skill should be easy to discover, easy to trigger, and narrow enough to be reliable in real usage.