QGIT - Git Release Management

Run QGIT to execute lint, typecheck, and test gates automatically before staging and committing. If any required gate fails, the commit is blocked and the failing output is displayed so you can fix issues first.

QGIT analyzes git status and diff output to determine the commit type and scope, then writes a description under 50 characters in imperative mood. It appends REQ references and co-author attribution following the Conventional Commits specification.

Yes, create a .qgit.json file in the project root defining custom gates with name, command, and required flag. You can add checks like security scans, bundle size limits, or test coverage thresholds alongside the default gates.

Yes, QGIT automatically excludes files matching patterns such as .env, *.key, *.pem, and credentials.json from staging. You can extend the exclusion list through the exclude_patterns field in .qgit.json.

The commit is blocked and a report shows which gate failed with error details, such as failing test names and locations. Fix the underlying issues, verify the gates pass, then rerun QGIT to commit.

Yes, use the --dry-run flag to run quality gates, analyze changes, and display the generated commit message and files that would be staged. No commit or push is performed in dry-run mode.