What problem does it solve? A Qlty check can report a red failure status with "Build errored. Check the log for more information." while its inline analysis comment shows no findings, leaving you unsure whether your code is broken or Qlty Cloud itself had an outage. This Skill separates transient infrastructure failures from real code defects so you do not waste time fixing code that is not broken. ## Core Features & Use Cases - Failure-mode triage: Distinguishes four verdicts (real crash, real findings, candidate outage, unknown) by reading the cloud build log rather than trusting the status text, which is identical across all cases. - Single evidence-backed retry: Re-triggers the cloud analysis with one empty commit whose header satisfies commitlint's type(#N): subject format, capped at one attempt before escalating. - Repository-shape awareness: Documents applicability across React SPA, Next.js app, and component-library shapes based on how .qlty/qlty.toml is tracked. - Use Case: Your pull request shows every required check green except Qlty, which failed in near-zero time with a clean inline comment. Use this Skill to inspect the build log, confirm a pipeline abort, and push one conforming empty commit to re-run the analysis. ## Quick Start Check whether the failing Qlty status on my pull request is a transient cloud outage and re-trigger the analysis once if it is.
