Maister Quick Bugfix FAQs

Question 1

What is the TDD Red/Green gate in this skill?

Accepted Answer

The TDD Red/Green gate ensures the bug is first reproduced with a failing test (Red) to prove the issue exists, followed by a fix that must pass the test (Green) to verify the resolution.

Question 2

What happens if the bug is too complex for a quick fix?

Accepted Answer

The skill performs a complexity check during analysis; if it detects architectural trade-offs or security-sensitive changes, it asks if you'd like to switch to a more formal development cycle.

Question 3

Does it support projects without an existing test suite?

Accepted Answer

Yes, while it prefers existing suites, it can create new test files following your project's conventions to satisfy the TDD reproduction requirement.

Question 4

When should I use Quick Bugfix instead of the full development workflow?

Accepted Answer

Use Quick Bugfix for well-scoped issues with clear reproduction steps. If the bug requires architectural changes or touches more than 5 files, the skill will automatically suggest escalating to the full development workflow.

Question 5

How does the skill know which coding standards to apply?

Accepted Answer

It scans your repository for a .maister/docs/INDEX.md file and reads specific documentation relevant to the bug area, such as API guidelines or frontend standards.

Maister Quick Bugfix

Key Features

Use Cases

Maister Quick Bugfix

Key Features

Use Cases