skills.rest
WikiEducationFoundation
WikiEducationFoundationOFFICIAL
Explore all skills by this author →
WebsiteGitHub

commit

Stage and format commit messages with Changes and Process sections.

427|723|Updated Dec 12, 2014
Search Tags:#git#workflow#commit#software-development#code-review#version-control#project-conventions
One-click install
npx skills add https://github.com/WikiEducationFoundation/WikiEduDashboard --skill commit-wikieducationfoundation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/WikiEducationFoundation/WikiEduDashboard/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/WikiEducationFoundation/WikiEduDashboard --skill commit-wikieducationfoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure commit messages follow the WikiEduDashboard format, reducing ambiguity and improving traceability across the project history.

Core Features & Use Cases

  • Enforces a clear subject line in the imperative mood (≤72 chars) and a structured body with a Changes and a Process section.
  • Guides the user through staged checks: git status, git diff --staged, and git diff to ensure intentional changes are captured.
  • Supports consistent documentation of session provenance and prompts as part of the commit process.

Quick Start

Draft and apply a structured commit using the project's format for the changes currently staged.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I format git commit messages for WikiEduDashboard conventions?▼

To format git commit messages for WikiEduDashboard, use an imperative subject line under 72 characters followed by structured Changes and Process sections, ensuring traceability and alignment with project standards.

What is the standard structure for a project conventions commit message?▼

A standard commit message for project conventions requires a concise imperative subject, a Changes section detailing edits, and a Process section documenting session provenance and workflow narrative.

How do I stage and check unstaged changes before making a git commit?▼

Before making a git commit, run git status to view changes, git diff --staged to review captured edits, and git diff to check unstaged changes, ensuring only intentional modifications are included.

Why does my commit message subject line fail version control checks?▼

Your commit message subject line fails version control checks if it exceeds 72 characters or lacks the imperative mood, enforced rules to maintain consistent software development history.

Can I document session provenance and prompts within my git workflow?▼

Yes, you can document session provenance and prompts within your git workflow by placing them in the Process section of the commit message, providing transparent context for code review and historical tracking.

Related Skills

Explore More Software Engineering Skills→
jaimedhenriquesjaimedhenriques

git-commit

Generate conventional git commits from repository diffs.

Community
Advanced
GlorktelligenceGlorktelligence

Git Workflow

Commit and push code changes to a remote repository using Conventional Commits.

Community
Intermediate
markus41markus41
1

gitworfkflows

Manage Git branching, commits, rebasing, and pull requests.

Community
Basic
popo0407popo0407

git-versioning

Standardizes GitHub version control with Git Flow and Conventional Commits.

Community
Intermediate