Run any Skill in Manus with one click

commit

Stars142

Forks116

UpdatedMarch 27, 2026 at 13:26

This skill should be used when the user asks to 'commit', 'create a commit', or 'git commit'. It creates conventional commits with FQCN scopes for Ansible collection content (roles, modules, plugins).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ansible-collections

ansible-collections/community.postgresql

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	commit
description	This skill should be used when the user asks to 'commit', 'create a commit', or 'git commit'. It creates conventional commits with FQCN scopes for Ansible collection content (roles, modules, plugins).

You are executing the commit skill. Follow these steps precisely.

Step 1: Determine Assisted-by

Identify the model you are currently running as from your system context. Format it as Assisted-by: <Model> <Version> — e.g. Claude Sonnet 4.6, GPT 5.3 Codex. This trailer will be appended to every commit created in this session.

Step 2: Infer commit type

Follow the Conventional Commits 1.0.0 standard.

Infer a commit type based on either a changelog fragment for the changes if present or on the nature of the changes made.

If the type is ambiguous, use AskUserQuestion to ask: "What type of change is this for <component>? (feat/fix/docs/chore/refactor/ci/deprecate/remove/breaking)"

Step 3: Draft commit message

Follow conventional commits format:

Component-specific: <type>(<component>): <imperative short description>
Project-level (no scope): <type>: <imperative short description>

Rules:

Subject line ≤ 72 characters
Lowercase after the colon and space
No trailing period
Use imperative mood (e.g. "add", "fix", "remove" — not "added", "fixes")
For breaking changes, append a blank line and BREAKING CHANGE: <explanation> in the body
Always append a blank line followed by Assisted-by: <AI tool/mode and its version> (from Step 1) at the end of every message

Examples:

feat: add support for custom agent port to postgresql_info module

Assisted-by: Claude Sonnet 4.6

feat!: drop support for ansible-core <= 2.16

BREAKING CHANGE: ansible-core 2.16 and earlier are no longer supported.

Assisted-by: Claude Sonnet 4.6

Step 4: Confirm with user

Use AskUserQuestion to present the proposed commit message and ask for approval:

"Proposed commit \n<message>\n\n\nApprove, or provide an edited message?"

If the user provides an edited message, use their version exactly.

Step 5: Commit

Run git add and commit.

More from this repository

same repository

pr-review

ansible-collections/community.postgresql

Reviews pull requests and code changes in this Ansible collection against project standards and the Ansible Collection Review Checklist. Use when asked to review a PR, patch, diff, or set of code changes. Do not use for GitHub Issues or general Q&A.

2026-03-27142

release

ansible-collections/community.postgresql

Guides the release of an Ansible collection following the upstream process (without release branches). Automatically determines the next version from changelog fragments. Outputs step-by-step instructions with commands for changelog generation, release PR, tagging, Galaxy publication, version bump, and GitHub release. Use when asked to release, publish, or tag a new collection version.

2026-03-27142

run-tests

ansible-collections/community.postgresql

Runs and writes tests (sanity, unit, integration) for the community.postgresql Ansible collection using ansible-test. Use when asked to run, check, or write tests for a module or utility. Do not use for PR reviews or questions unrelated to testing.

2026-03-27142

name	commit
description	This skill should be used when the user asks to 'commit', 'create a commit', or 'git commit'. It creates conventional commits with FQCN scopes for Ansible collection content (roles, modules, plugins).

You are executing the commit skill. Follow these steps precisely.

Step 1: Determine Assisted-by

Step 2: Infer commit type

Follow the Conventional Commits 1.0.0 standard.

Infer a commit type based on either a changelog fragment for the changes if present or on the nature of the changes made.

If the type is ambiguous, use AskUserQuestion to ask: "What type of change is this for <component>? (feat/fix/docs/chore/refactor/ci/deprecate/remove/breaking)"

Step 3: Draft commit message

Follow conventional commits format:

Component-specific: <type>(<component>): <imperative short description>
Project-level (no scope): <type>: <imperative short description>

Rules:

Subject line ≤ 72 characters
Lowercase after the colon and space
No trailing period
Use imperative mood (e.g. "add", "fix", "remove" — not "added", "fixes")
For breaking changes, append a blank line and BREAKING CHANGE: <explanation> in the body
Always append a blank line followed by Assisted-by: <AI tool/mode and its version> (from Step 1) at the end of every message

Examples:

feat: add support for custom agent port to postgresql_info module

Assisted-by: Claude Sonnet 4.6

feat!: drop support for ansible-core <= 2.16

BREAKING CHANGE: ansible-core 2.16 and earlier are no longer supported.

Assisted-by: Claude Sonnet 4.6

Step 4: Confirm with user

Use AskUserQuestion to present the proposed commit message and ask for approval:

"Proposed commit \n<message>\n\n\nApprove, or provide an edited message?"

If the user provides an edited message, use their version exactly.

Step 5: Commit

Run git add and commit.