Verified:GitHub

wa:dev-commit

Stages and commits code changes using a two-stage workflow with conventional-commit validation.

Updated Mar 26, 2026

Search Tags:#git #developer workflow #conventional commits #staging #e2e testing #commit validation #security guardrails

Ready to run

npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wa:dev-commit
Source: https://github.com/jeremy-newhouse/eck-e2e-weather-app/tree/main/.claude/skills/dev-commit
Command: npx skills add https://github.com/jeremy-newhouse/eck-e2e-weather-app --skill wa-dev-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents accidental or unsafe commits by guiding you through staging changes and enforcing conventional-commit message validation before creating the commit.

Core Features & Use Cases

Safe staging with guardrails: Stages only intended files (by provided paths or inferred task-relevant changes) while excluding .env files, credentials, and build artifacts unless explicitly requested.
Conventional commit message generation & validation: Creates a commit message from the staged-change context and validates it against allowed conventional commit types.
Two-stage workflow with clear progress: Updates a statusline at the start of each stage and resets it on completion or error.
Use Case: When implementing a small feature like adding authentication, you can stage the relevant code and tests, generate a feat-prefixed conventional commit message, validate it, and commit without risking secrets or malformed messages.

Quick Start

Use the wa:dev-commit skill with a conventional commit message like "/wa:dev-commit feat: add user authentication".

Frequently Asked Questions about wa:dev-commit

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

FAQPage Schema

How do I stage and commit code changes while preventing accidental secrets exposure?▼

To stage and commit code changes safely, you can use a workflow that explicitly excludes .env files, credentials, and build artifacts from the working tree before creating the git commit. This prevents accidental secrets exposure by validating staged files against strict guardrails.

How do I validate conventional commit messages before creating a git commit?▼

You can validate conventional commit messages by generating a message from staged-change context and checking it against allowed conventional commit types before running git commit. This validation ensures your commit prefix and format meet conventional standards.

Can I automatically generate a commit message from my staged code changes?▼

Yes, you can automatically generate a commit message from staged-change context. The workflow summarizes your staged files and uses that context to create a conventional commit message, which is then validated before the commit is created.

Does this staging workflow support committing specific file paths?▼

Yes, the staging workflow supports committing specific file paths. You can optionally provide explicit file paths to stage, or rely on inferred task-relevant changes in the working tree, ensuring only intended files are committed.

What is the best way to ensure only intended files are staged for a feature update?▼

The best way to ensure only intended files are staged is to use a safe staging process with guardrails that stages files by provided paths or inferred task-relevant changes. This strictly excludes secrets, environment files, and build artifacts unless explicitly requested.

Why should I use a two-stage workflow for git commits?▼

You should use a two-stage workflow for git commits to separate file staging from commit creation, applying message validation in between. This structured approach updates status indicators at each stage and resets them on completion or error, providing robust error handling.