Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

$pwd:

conventional-commit

Name: Conventional Commit
Author: NethServer

// Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Ejecutar en Manus

$ git log --oneline --stat

stars:1

forks:0

updated:28 de abril de 2026, 12:56

SKILL.md

readonly

name

conventional-commit

description

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Git Commit with Conventional Commits

Overview

Create standardized, semantic git commits using the Conventional Commits specification. Analyze the actual diff to determine appropriate type, scope, and message. Conventional commits specifications: https://www.conventionalcommits.org/en/v1.0.0/

Conventional Commit Format

<type>[optional scope]: <description>

<body>

[optional footer(s)]

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting/style (no logic)
`refactor`	Code refactor (no feature/fix)
`perf`	Performance improvement
`test`	Add/update tests
`build`	Build system/dependencies
`ci`	CI/config changes
`chore`	Maintenance/misc
`revert`	Revert commit

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

AI Agent Footers

AI agents MUST NOT add Signed-off-by tags. Only humans can legally be author of a commit.

When AI tools contribute to development, proper attribution helps track the evolving role of AI in the development process.

Contributions MUST include a Assisted-by tag in the following format::

Assisted-by: AGENT_NAME:MODEL_VERSION

Where:

AGENT_NAME is the name of the AI tool or framework
MODEL_VERSION is the specific model version used

Example:

Assisted-by: Copilot:gpt-54-mini

Workflow

1. Analyze Diff

# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

Type: What kind of change is this?
Scope: What area/module is affected?
Description: One-line summary of what changed (present tense, imperative mood, <72 chars)

4. Execute Commit

# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<body>

<optional footer>
EOF
)"

Commit rules

One logical change per commit
Separate subject from body with a blank line
Limit the subject line to 50 characters
Capitalize the subject line
Do not end the subject line with a period
Present tense: "add" not "added"
Imperative mood: "fix bug" not "fixes bug"
Reference issues: Closes #123, Refs #456
Always include a description body
Use the body to explain what and why, not how
Wrap the description body at 72 characters

Git Safety Protocol

NEVER update git config
NEVER run destructive commands (--force, hard reset) without explicit request
NEVER skip hooks (--no-verify) unless user asks
NEVER force push to main/master
If commit fails due to hooks, fix and create NEW commit (don't amend)

related-skills.json

mismo repositorio

nethserver-containerfile.md

from "NethServer/agents"

Write and review secure, production-ready Containerfiles following NethServer container best practices. Use when creating a new Containerfile, reviewing an existing container image, or mentions "/Containerfile". Supports: (1) Rootless container configuration with non-root USER, (2) Multi-stage build separation of build and runtime, (3) Minimal and pinned base image selection (Alpine/Debian-slim), (4) Vulnerability scanning guidance with Trivy and layer inspection with Dive, (5) Renovate setup for automated dependency updates

2026-04-281

nethserver-issue.md

from "NethServer/agents"

Write well-structured GitHub issues following NethServer contribution guidelines. Use when the user asks to open an issue, file a bug report, request a feature, or mentions "/issue". Supports: (1) Bug report template with component, reproduction steps, and expected behavior, (2) Feature request template with user value and references, (3) Issue type selection (Bug/Feature/Design/Backend/Frontend/Task/Draft), (4) Label guidance (testing, verified, milestone goal), (5) Security vulnerability reporting rules and correct tracker URLs

2026-04-281

nethserver-pr.md

from "NethServer/agents"

Create and manage pull requests following NethServer contribution conventions. Use when the user asks to open a PR, submit a contribution, or mentions "/pr". Supports: (1) PR title and description structure with a ready-to-use template, (2) Correct issue link format for NethServer/NethVoice and NethSecurity, (3) Reviewer and self-assignee selection, (4) Merge commit conventions with issue references for automation, (5) Draft PR guidance for work-in-progress contributions

2026-04-281

nethserver-release.md

from "NethServer/agents"

Create NethServer module or package releases following semver and project-specific versioning rules. Use when the user asks to release a new version, tag a release, bump a version number, or mentions "/release". Defaults to testing/pre-release unless stable is explicitly requested. Supports: (1) Version increment decision (major/minor/patch), (2) Testing pre-release by default (X.Y.Z-testing.N suffix), (3) Stable release only on explicit user request, (4) NethServer 8/NethVoice via gh ns8-release-module, (5) NethSecurity OpenWrt versioning conventions

2026-04-281

package.json

"author": "NethServer"

"repository": "NethServer/agents"

Abrir repositorio de GitHub Ver repositorios del creador

$ install --global

$ download --local

Ejecutar en Manus

$ useful --forSOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas15-1252L4

name

conventional-commit

description

Git Commit with Conventional Commits

Overview

Conventional Commit Format

<type>[optional scope]: <description>

<body>

[optional footer(s)]

Commit Types

Type	Purpose
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting/style (no logic)
`refactor`	Code refactor (no feature/fix)
`perf`	Performance improvement
`test`	Add/update tests
`build`	Build system/dependencies
`ci`	CI/config changes
`chore`	Maintenance/misc
`revert`	Revert commit

Breaking Changes

# Exclamation mark after type/scope
feat!: remove deprecated endpoint

# BREAKING CHANGE footer
feat: allow config to extend other configs

BREAKING CHANGE: `extends` key behavior changed

AI Agent Footers

AI agents MUST NOT add Signed-off-by tags. Only humans can legally be author of a commit.

When AI tools contribute to development, proper attribution helps track the evolving role of AI in the development process.

Contributions MUST include a Assisted-by tag in the following format::

Assisted-by: AGENT_NAME:MODEL_VERSION

Where:

AGENT_NAME is the name of the AI tool or framework
MODEL_VERSION is the specific model version used

Example:

Assisted-by: Copilot:gpt-54-mini

Workflow

1. Analyze Diff

# If files are staged, use staged diff
git diff --staged

# If nothing staged, use working tree diff
git diff

# Also check status
git status --porcelain

2. Stage Files (if needed)

If nothing is staged or you want to group changes differently:

# Stage specific files
git add path/to/file1 path/to/file2

# Stage by pattern
git add *.test.*
git add src/components/*

# Interactive staging
git add -p

Never commit secrets (.env, credentials.json, private keys).

3. Generate Commit Message

Analyze the diff to determine:

Type: What kind of change is this?
Scope: What area/module is affected?
Description: One-line summary of what changed (present tense, imperative mood, <72 chars)

4. Execute Commit

# Single line
git commit -m "<type>[scope]: <description>"

# Multi-line with body/footer
git commit -m "$(cat <<'EOF'
<type>[scope]: <description>

<body>

<optional footer>
EOF
)"

Commit rules

One logical change per commit
Separate subject from body with a blank line
Limit the subject line to 50 characters
Capitalize the subject line
Do not end the subject line with a period
Present tense: "add" not "added"
Imperative mood: "fix bug" not "fixes bug"
Reference issues: Closes #123, Refs #456
Always include a description body
Use the body to explain what and why, not how
Wrap the description body at 72 characters

Git Safety Protocol

NEVER update git config
NEVER run destructive commands (--force, hard reset) without explicit request
NEVER skip hooks (--no-verify) unless user asks
NEVER force push to main/master
If commit fails due to hooks, fix and create NEW commit (don't amend)

conventional-commit

Git Commit with Conventional Commits

Overview

Conventional Commit Format

Commit Types

Breaking Changes

AI Agent Footers

Workflow

1. Analyze Diff

2. Stage Files (if needed)

3. Generate Commit Message

4. Execute Commit

Commit rules

Git Safety Protocol

Más de este repositorio

Más de este repositorio

Git Commit with Conventional Commits

Overview

Conventional Commit Format

Commit Types

Breaking Changes

AI Agent Footers

Workflow

1. Analyze Diff

2. Stage Files (if needed)

3. Generate Commit Message

4. Execute Commit

Commit rules

Git Safety Protocol