Commit Majiayu000

Name: Commit Majiayu000
Author: diegosouzapw

ASecurity

Generates commit messages and creates commits. Use when writing commit messages, committing changes, or reviewing staged changes.

57 stars
0 votes
0 copies
0 views
Added October 17, 2026

code-qualitygitci/cddocumentation

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill commit-majiayu000 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Commit Majiayu000?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Commit Majiayu000

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-commit-majiayu000-4a8fdda7/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-commit-majiayu000-4a8fdda7)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: commit
description: Generates commit messages and creates commits. Use when writing commit messages, committing changes, or reviewing staged changes.
---

# Commit Messages

Use [Conventional Commits](https://www.conventionalcommits.org/) format.

## Format

```text
<type>(<scope>): <description>

[optional body]
```

## Types

- `feat`: User-facing features or behavior changes (must change production code)
- `fix`: Bug fixes (must change production code)
- `docs`: Documentation only
- `style`: Code style/formatting (no logic changes)
- `refactor`: Code restructuring without behavior change
- `test`: Adding or updating tests
- `chore`: CI/CD, tooling, dependency bumps, configs (no production code)

## Scopes

Optional. Use when it adds clarity. Examples: `cloudfront`, `s3`, `ci`.

## Breaking Changes

Use `!` suffix: `feat!: remove deprecated resource`

## Examples

```text
feat(cloudfront): add immutable cache headers
fix: correct CloudFront Function ARN attribute
chore: add husky pre-commit hooks
docs: update architecture documentation
```

## Instructions

1. Run `git diff --staged` to see staged changes
2. Analyze the changes and determine the appropriate type
3. Write a concise description (under 72 characters)
4. Add body only if the "why" isn't obvious from the description