Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

commit

Étoiles4

Forks2

Mis à jour31 janvier 2026 à 00:04

Create a git commit following project conventions. Use when the user asks to commit changes or create a commit.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

nikuscs

nikuscs/olx-tracker

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	commit
description	Create a git commit following project conventions. Use when the user asks to commit changes or create a commit.
disable-model-invocation	true
allowed-tools	Bash(git *)

Create Git Commit

Follow the project's git commit conventions to create a well-formed commit.

Workflow

Check status and diff:

git status
git diff --stat
git diff
git log --oneline -5  # See recent commit style

Analyze changes and draft a commit message:
- Identify the nature of changes (feature, fix, refactor, test, docs, chore)
- Use appropriate prefix: feat:, fix:, test:, docs:, refactor:, chore:
- Write concise summary (50-72 chars)
- Add detailed body if needed
Stage and commit:

# Stage specific files (preferred over git add -A)
git add <file1> <file2> <file3>

# Create commit with heredoc for proper formatting
git commit -m "$(cat <<'EOF'
<type>: <summary>

<optional detailed body>

EOF
)"

# Verify commit was created
git status

Commit Message Format

<type>: <short summary in imperative mood>

<optional longer description explaining WHY, not WHAT>

Types

feat: New feature
fix: Bug fix
test: Add or update tests
docs: Documentation changes
refactor: Code refactoring
chore: Maintenance tasks
perf: Performance improvements

Examples

test: add comprehensive HTTP mocking tests for API client

- Add 19 new wiremock-based tests for src/api/client.rs
- Improve coverage from 34.1% to 88.9% (+54.8pp)
- Test all search parameters, error handling, and pagination
- All tests properly mocked with NO real API calls

feat: add HTTP server with API key authentication

Add axum-based HTTP API server exposing all CLI functionality.
Includes background daemon support and request timeout config.

Safety Rules

NEVER use --no-verify or skip hooks
NEVER commit sensitive files (.env, credentials, tokens)
NEVER use git add -A or git add . (add specific files)
NEVER amend commits unless explicitly requested
NEVER force push to main/master

When $ARGUMENTS is provided

Use it as the commit summary and follow the same format:

git commit -m "$(cat <<'EOF'
$ARGUMENTS
EOF
)"

Plus depuis ce dépôt

même dépôt

olx-tracker

nikuscs/olx-tracker

Search OLX.pt listings, track prices, and detect deals. Use for finding products, monitoring prices, and getting alerts on good deals in Portugal and other OLX regions.

2026-05-124

add-filter

nikuscs/olx-tracker

Create a new filter for the tracker system. Use when adding custom filtering logic or when the user asks to create a filter.

2026-01-314

add-notifier

nikuscs/olx-tracker

Create a new notification backend (e.g., Telegram, Email, Slack). Use when adding custom notification channels.

2026-01-314

build

nikuscs/olx-tracker

Build the olx-tracker project. Use when compiling the project or when the user asks to build.

2026-01-314

lint

nikuscs/olx-tracker

Check code quality and formatting. Use when checking code style, running pre-commit checks, or when the user asks to lint or format code.

2026-01-314

run-tracker

nikuscs/olx-tracker

Run olx-tracker CLI commands. Use when executing tracker operations, managing searches, or testing the application.

2026-01-314

Create Git Commit

Follow the project's git commit conventions to create a well-formed commit.

Workflow

Check status and diff:

git status git diff --stat git diff git log --oneline -5 # See recent commit style

Analyze changes and draft a commit message:

Identify the nature of changes (feature, fix, refactor, test, docs, chore)
Use appropriate prefix: feat:, fix:, test:, docs:, refactor:, chore:
Write concise summary (50-72 chars)
Add detailed body if needed

Stage and commit:

# Stage specific files (preferred over git add -A) git add <file1> <file2> <file3> # Create commit with heredoc for proper formatting git commit -m "$(cat <<'EOF' <type>: <summary> <optional detailed body> EOF )" # Verify commit was created git status

Commit Message Format

<type>: <short summary in imperative mood> <optional longer description explaining WHY, not WHAT>

Types

feat: New feature

fix: Bug fix

test: Add or update tests

docs: Documentation changes

refactor: Code refactoring

chore: Maintenance tasks

perf: Performance improvements

Examples

test: add comprehensive HTTP mocking tests for API client - Add 19 new wiremock-based tests for src/api/client.rs - Improve coverage from 34.1% to 88.9% (+54.8pp) - Test all search parameters, error handling, and pagination - All tests properly mocked with NO real API calls

feat: add HTTP server with API key authentication Add axum-based HTTP API server exposing all CLI functionality. Includes background daemon support and request timeout config.

Safety Rules

NEVER use --no-verify or skip hooks

NEVER commit sensitive files (.env, credentials, tokens)

NEVER use git add -A or git add . (add specific files)

NEVER amend commits unless explicitly requested

NEVER force push to main/master

When $ARGUMENTS is provided

Use it as the commit summary and follow the same format:

git commit -m "$(cat <<'EOF' $ARGUMENTS EOF )"