### Conventional Commit Naming Examples

Source: https://context7.com/yoonsin91/ai-skills-pack/llms.txt

Illustrates good and bad naming conventions for AI skills, emphasizing the use of gerunds, lowercase letters, numbers, and hyphens, while avoiding vague or reserved terms.

```markdown
# Good naming examples:
- processing-pdfs
- analyzing-spreadsheets
- managing-databases
- testing-code
- writing-documentation

# Acceptable alternatives:
- pdf-processing
- spreadsheet-analysis
- process-pdfs
- analyze-spreadsheets

# Avoid these patterns:
- helper, utils, tools (too vague)
- anthropic-helper, claude-tools (reserved words)
```

--------------------------------

### Drafting Conventional Commits Skill - SKILL.md

Source: https://context7.com/yoonsin91/ai-skills-pack/llms.txt

Defines the 'drafting-conventional-commits' skill, including its name, description, workflow, commit types, and examples of input and output for generating Conventional Commits messages.

```yaml
---
name: drafting-conventional-commits
description: "Draft a Conventional Commits message from either a short summary
of changes or by inspecting the local git diff."
---

# Workflow:
# 1. Read user summary or inspect git status/diff
# 2. Infer commit type from changes
# 3. Identify optional scope (subsystem/module)
# 4. Draft concise subject in imperative mood
# 5. Add body explaining why (not how)
# 6. Add footers for breaking changes or issue refs

# Commit Types:
# feat     - New user-facing behavior
# fix      - Bug fix
# docs     - Documentation only
# style    - Formatting (no behavior change)
# refactor - Refactor without behavior change
# perf     - Performance improvement
# test     - Tests only
# build    - Build system/dependencies
# ci       - CI config/pipeline
# chore    - Maintenance chores
# revert   - Revert of prior commit

# Example Inputs and Outputs:

Input: "add pagination to the invoices list"
Output:
feat(invoices): add pagination to list

Input: "fix crash when opening empty cart; breaking API change: remove legacy cart token"
Output:
fix(cart)!: prevent crash on empty cart

BREAKING CHANGE: remove legacy cart token

Input: "update readme with setup steps"
Output:
docs(readme): add setup steps
```

--------------------------------

### Skill Structure Definition

Source: https://context7.com/yoonsin91/ai-skills-pack/llms.txt

Defines the standard directory structure for an AI skill within the project. It includes the required SKILL.md file and optional directories for scripts, references, and assets.

```tree
skill-name/
├── SKILL.md          # Required: name, description, and usage workflow
├── scripts/          # Optional: reusable automation scripts
├── references/       # Optional: domain documentation
└── assets/           # Optional: templates or files used in outputs
```

--------------------------------

### Drafting PR Descriptions Skill - SKILL.md

Source: https://context7.com/yoonsin91/ai-skills-pack/llms.txt

Defines the 'drafting-pr-descriptions' skill, outlining its purpose to generate pull request descriptions from git information and a provided template. It also lists data collection commands and a sample PR template structure.

```yaml
---
name: drafting-pr-descriptions
description: Summarize code changes on the current git branch and draft a
pull request description using a provided template.
---

# Data Collection Commands:
git rev-parse --show-toplevel      # Get repo root
git branch --show-current          # Get current branch name
git status -sb                     # Short status with branch info
git log --oneline <base>..HEAD     # Committed changes since base
git diff --stat <base>...HEAD      # Diff stats against base
git diff --stat                    # Uncommitted changes
git diff --stat --cached           # Staged changes

# PR Template (references/pr-template.md):
### Describe your changes
# Summary of the changes and the related issue

### How Has This Been Tested?
# Description of tests run to verify changes

### What to review?
# What reviewers should pay attention to

### Self Checklist:
- [ ] I have performed a self-review of my code.
- [ ] I have added tests that prove my fix is effective or that my feature works.
- [ ] New and existing unit tests pass locally with my changes.
- [ ] I have commented my code, particularly in hard-to-understand areas.
- [ ] I have made corresponding changes to the documentation.

# Workflow:
# 1. Identify repo and current branch

```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.