wa:dev-commit

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.

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.

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.

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.

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.

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.