Keep Flask request connections from leaking on error paths: Perch rule pack

1 saved requirement for Flask. Inspect the selectors and adapt the example paths to your repository.

- name: request-db-cleanup
  where: "database.py"
  ensure: >-
    close_db must close a database connection removed from g, and init_app must register close_db as teardown_appcontext.

Download the rule pack ZIP · Download YAML · Agent repair task · Implementation, integration requirements and captured checks

Install the rule without replacing your configuration

npm install -g @lakeday/perch
perch login
curl -fL 'https://reporules.fyi/flask/request-db-cleanup/rule-pack.zip' -o 'perch-guide-flask-request-db-cleanup.zip'
unzip -n 'perch-guide-flask-request-db-cleanup.zip'

Keep your existing perch.yaml. Extraction preserves existing files and adds .perch/rules/perch-guide-flask-request-db-cleanup.yaml. Review each where selector before running a check on your application.

Configure your coding agent

perch setup claude-code
perch setup codex
perch setup cursor
perch setup pi

Choose the setup command for the agent you use.

Check the edit, fix the finding, check again

perch check database.py --rules request-db-cleanup --json

Run the check after an agent edit. Read the finding and affected code, repair the implementation, and repeat the identical command. Keep the application regression tests as separate gates.

Exit 3 means a finding. Exit 1 or 2 means the check did not complete. A pass does not prove application correctness. Fresh judgments can vary; unchanged requests reuse cached answers. Relevant source is sent to the configured model service.

Pack manifest and SHA-256 hash · Pack README