Work through C++ examples of real application boundaries: Protect Qt’s shared stock decision with one scoped mutex; Dispose Qt network replies after their completion signal. Each recipe includes implementation code, integration prerequisites, failure-path tests to add, a Perch rule, and the captured broken/fixed source checks.
Download the Qt rule pack ZIP · Inspect the YAML rules
C++
The availability check and decrement form one critical section. Locking only the decrement still permits two readers to decide against the same old count. RAII releases the mutex on every return path.
Broken edit flagged · corrected edit passes
C++
A QNetworkReply remains an owned resource after the request finishes. Deferred deletion avoids deleting it directly from a signal callback while Qt is still delivering that signal. The owner destruction path aborts pending work; reply lifetime remains tied to completion and the manager.
Broken edit flagged · corrected edit passes
Choose the failure you need to prevent, add the scoped rule to your repository, and check both the broken and corrected implementation. Ask your agent to inspect the finding, repair the code and recheck the same rule. Keep framework tests beside the model check.
Perch keeps the requirement beside the code. Reuse the named check during the agent’s next edit and in CI, with cached answers free on unchanged requests.
Official Qt documentation · All language and framework recipes
