Pre-Push Quality Guard FAQs

Question 1

Can this skill be integrated with implementation planning?

Accepted Answer

Absolutely. It is designed to be the final verification step in any implementation plan, ensuring that the finished feature is fully compliant with project standards.

Question 2

Does this skill fix errors automatically?

Accepted Answer

Yes, it executes 'bun run fix' and 'bun run format' to automatically resolve all fixable linting and styling issues before proceeding to manual checks.

Question 3

Why is 'bun install' mandatory in the workflow?

Accepted Answer

It ensures that the environment has the latest dependencies and type definitions, preventing false positives or missed errors during the linting and type-checking phases.

Question 4

When should I skip using this quality check?

Accepted Answer

You can safely skip this skill for changes that do not affect the source code, such as updates to documentation (README.md), environment variables (.env), or git configuration files.

Question 5

What if the code has existing errors I didn't cause?

Accepted Answer

This skill enforces a zero-tolerance policy. To maintain code integrity, all detected errors must be fixed, regardless of whether they are new or pre-existing, before a push is allowed.

Pre-Push Quality Guard

About

Key Features

Use Cases

Pre-Push Quality Guard

About

Key Features

Use Cases