OpenResty: Perch rule pack
2 saved requirements for OpenResty. Inspect the selectors and adapt the example paths to your repository.
- name: shared-stock-availability
where: "lua/reserve.lua"
ensure: >-
Inside the acquired inventory lock, reserve must reject available < quantity before changing the shared dictionary.
- name: timer-admission-must-succeed
where: "lua/queue_receipt.lua"
ensure: >-
enqueue must handle ngx.timer.at failure with a service-unavailable response before reporting accepted.
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/openresty/rule-pack.zip' -o 'perch-guide-openresty.zip'
unzip -n 'perch-guide-openresty.zip'Keep your existing perch.yaml. Extraction preserves existing files and adds .perch/rules/perch-guide-openresty.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 piChoose the setup command for the agent you use.
Check the edit, fix the finding, check again
perch check lua/reserve.lua --rules shared-stock-availability --json
perch check lua/queue_receipt.lua --rules timer-admission-must-succeed --jsonRun 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.