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

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

commit-style

Étoiles0

Forks0

Mis à jour12 juin 2026 à 10:02

Team commit-message conventions. Use when writing a commit message, committing or amending changes, or when asked about the project's commit format. Reads the per-project style from .claude/idev/commit-style.md.

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

TheophilusChinomona

TheophilusChinomona/idev

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-style
description	Team commit-message conventions. Use when writing a commit message, committing or amending changes, or when asked about the project's commit format. Reads the per-project style from .claude/idev/commit-style.md.

Commit Style — Team Commit Message Conventions

Write commit messages that pass the team's commit-msg hook on the first try and read well in git log years later.

Procedure

Read the project's style file first: .claude/idev/commit-style.md. If it exists, its rules override everything below. If it doesn't exist, apply the defaults below (and mention that /idev:hooks install-git-hooks sets up the style file + enforcement hooks).
Derive the ticket ID from the branch name when the style requires one: git branch --show-current, extract the first ABC-123-shaped token. The prepare-commit-msg hook does this automatically too — don't add the prefix twice.
Write the message:
- Subject: type(scope): imperative summary — conventional-commit types (feat, fix, docs, refactor, perf, test, build, ci, chore), ≤ 72 chars, no trailing period.
- Body (for anything non-trivial): the why, not a list of what — the diff already shows what. Wrap at ~72 columns.
- Trailers last, each on its own line (Co-Authored-By:, Refs:), per the team's policy in the style file.
Check before committing: if .git/hooks/commit-msg exists, the message must match its pattern (default: optional ABC-123: ticket prefix + conventional-commit subject). If the hook rejects a commit, fix the message — never bypass with --no-verify unless the user explicitly asks.

Defaults (when no style file exists)

feat(auth): add refresh-token rotation

Sessions died after 15 minutes because the access token was never
refreshed. Rotate the refresh token on each renewal per OWASP.

Refs: ABC-123

Pull request format

When creating a PR (any platform — az repos pr create on Azure DevOps, gh pr create on GitHub), unless .claude/idev/commit-style.md overrides:

Title: same convention as the commit subject (ticket prefix + typed imperative summary). For a single-commit branch, reuse the subject.
Description:

## What
2-4 bullets of user-visible change (not a commit list — the platform shows those).

## Why
The problem/ticket context in 1-3 sentences.

## Testing
What was actually run: build, tests, browser-test report path if UI.

## Notes for reviewer
Risky spots, decisions needing eyes, rollback hint. Omit if none.

Anti-patterns

"fix stuff", "wip", "updates" — the hook rejects these; so should you.
Restating the diff in the body.
Bundling unrelated changes to share one message — split the commits.

Plus depuis ce dépôt

même dépôt

codebase-explainer

TheophilusChinomona/idev

Turn a codebase into an onboarding playlist — Claude-authored analysis docs plus NotebookLM explainer videos (one overview + one per subsystem). Use when asked to explain a codebase, onboard onto a repo, make explainer/walkthrough videos of the code, or 'help me understand how this whole thing works'.

2026-06-250

branch-sync

TheophilusChinomona/idev

Syncs the current feature branch with the team base branch (merge base into feature) before creating a PR, resolving merge conflicts safely with build/test verification. Use when preparing a branch for a PR, when asked to sync with or merge in the base/developer branch, when a PR shows conflicts, or before pushing a long-lived feature branch.

2026-06-120

idev-init

TheophilusChinomona/idev

Scaffolds the per-project .claude/idev/ state directory (caches, journal, lessons, config templates) for the idev plugin. Use when starting idev in a new project, when the SessionStart hook reports the state directory is missing, or when the user runs /idev:idev-init or asks to 'set up idev'.

2026-06-120

skill-benchmark

TheophilusChinomona/idev

Evaluates and benchmarks Agent Skill quality via static analysis and evaluation methodology. Use when assessing or reviewing skill quality, benchmarking skills, measuring skill activation accuracy, optimizing skill descriptions, or running /idev:benchmark-skills.

2026-06-120

smart-context

TheophilusChinomona/idev

Token-optimized context loading: load the cached project index at session start, then Grep before Read, expanding only as needed. Use when starting a session, deciding what context to load, or generating/refreshing the project index. For feature-name → file-path lookups, the file-index skill answers directly from this index.

2026-06-120

strategic-compact

TheophilusChinomona/idev

Suggests manual /compact at logical task boundaries (after exploration, planning, milestones) instead of arbitrary auto-compaction. Use when the user wants automatic /compact reminders, asks about managing context size, or when deciding whether to suggest compaction at a phase boundary.

2026-06-120

Commit Style — Team Commit Message Conventions

Write commit messages that pass the team's commit-msg hook on the first try and read well in git log years later.

Procedure

Read the project's style file first: .claude/idev/commit-style.md. If it exists, its rules override everything below. If it doesn't exist, apply the defaults below (and mention that /idev:hooks install-git-hooks sets up the style file + enforcement hooks).

Derive the ticket ID from the branch name when the style requires one: git branch --show-current, extract the first ABC-123-shaped token. The prepare-commit-msg hook does this automatically too — don't add the prefix twice.

Write the message:

Subject: type(scope): imperative summary — conventional-commit types (feat, fix, docs, refactor, perf, test, build, ci, chore), ≤ 72 chars, no trailing period.
Body (for anything non-trivial): the why, not a list of what — the diff already shows what. Wrap at ~72 columns.
Trailers last, each on its own line (Co-Authored-By:, Refs:), per the team's policy in the style file.

Check before committing: if .git/hooks/commit-msg exists, the message must match its pattern (default: optional ABC-123: ticket prefix + conventional-commit subject). If the hook rejects a commit, fix the message — never bypass with --no-verify unless the user explicitly asks.

Defaults (when no style file exists)

feat(auth): add refresh-token rotation Sessions died after 15 minutes because the access token was never refreshed. Rotate the refresh token on each renewal per OWASP. Refs: ABC-123

Pull request format

When creating a PR (any platform — az repos pr create on Azure DevOps, gh pr create on GitHub), unless .claude/idev/commit-style.md overrides:

Title: same convention as the commit subject (ticket prefix + typed imperative summary). For a single-commit branch, reuse the subject.

Description:

## What 2-4 bullets of user-visible change (not a commit list — the platform shows those). ## Why The problem/ticket context in 1-3 sentences. ## Testing What was actually run: build, tests, browser-test report path if UI. ## Notes for reviewer Risky spots, decisions needing eyes, rollback hint. Omit if none.

Anti-patterns

"fix stuff", "wip", "updates" — the hook rejects these; so should you.

Restating the diff in the body.

Bundling unrelated changes to share one message — split the commits.