// Automates the full commit workflow: analyzes changes, writes commit message, stages files, commits, and handles test failures by fixing them until the commit succeeds. Use when the user wants to commit their changes.
| name | checkin |
| description | Automates the full commit workflow: analyzes changes, writes commit message, stages files, commits, and handles test failures by fixing them until the commit succeeds. Use when the user wants to commit their changes. |
Automates the full commit workflow: analyzes changes, writes commit message, stages files, commits, and handles pre-commit hook failures by fixing test failures until the commit succeeds.
Run these commands in parallel to understand the current state:
git status
git diff
git diff --staged
From this analysis:
Before committing, verify the code compiles and tests pass:
# Build the solution
dotnet build agg-sharp.sln
# Run all tests
dotnet test Tests/Agg.Tests/Agg.Tests.csproj
If tests fail, fix them before proceeding. Use the fix-test-failures skill.
git addgit commit -m "$(cat <<'EOF'
Commit message here.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
EOF
)"
If the commit fails due to pre-commit hooks:
fix-test-failures skill to diagnose and fixRepeat Step 4 until the commit succeeds. Each iteration:
Use --amend only when:
Otherwise, create a new commit with the fixes.
After a successful commit:
git status to verify the commit succeeded--no-verify to bypass hooksFix every single error. No exceptions.
When errors occur during the commit process:
Take the hard path:
Quality matters. Every error is an opportunity to make the code better. The easy path creates technical debt; the hard path creates code we can be proud of.
This skill provides guidance for fixing file size violations detected by FileComplianceTests. Use when a C# file exceeds its line limit (800 lines default, or explicit limit for legacy files). The skill explains strategies to reduce file size while maintaining code quality.
This skill should be used after running tests when failures occur. It provides a systematic approach to diagnosing test failures through instrumentation and root cause analysis.
This skill provides guidance on writing and running tests in this project. It should be used when writing new tests, understanding the test infrastructure, or making decisions about what to test. Covers TUnit configuration, unit tests, automation tests, and testing best practices.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.