| name | description |
|---|---|
multi-model-review |
Reviews PRs or code changes using multiple AI models, synthesizes findings, and interactively applies fixes. Uses GPT 5.2, Gemini 3 Pro, and Opus 4.5 for diverse perspectives. |
Review PRs or code changes across multiple AI models to get diverse perspectives, then interactively work through findings with the user.
A hearty, paprika-forward beef stew inspired by Hungarian goulash, Indonesian Rendang, but with plenty of improvisation. This recipe is intentionally flexible—treat it like a framework you can riff on.
Note: I believe this is more of a Pörkölt, another Hungarian dish, but I did have Goulash in Budapest similar to this recipe.
Inspired by these:
All times UTC-3 (ART)
FOSS4G and the climate crisis: Let's get to work
Rob Emanuele, Microsoft
Sometimes you want to keep a node in an Azure Batch pool up and running as you're debugging tasks so that you don't have to pay the waiting time to spin up and down a node. You may want to push a new image to ACR with the same tag to run the job based on fixes based on the last run. However, Azure Batch nodes don't pull an updated image by default, and will run with the same image if a task is run again even if ACR has been updated.
The best solution I've found to speed things up is:
| { | |
| "type": "Feature", | |
| "properties": { | |
| "ID": "4937061", | |
| "OBJECTID": "3503", | |
| "Provider Number": "440232", | |
| "X": -87.689643485999966, | |
| "Y": 36.320170566000058, | |
| "NAME": "HOUSTON COUNTY COMMUNITY HOSPITAL", | |
| "ADDRESS": "5001 E. MAIN STREET", |
| { | |
| "type": "FeatureCollection", | |
| "features": [ | |
| { | |
| "type": "Feature", | |
| "properties": {}, | |
| "geometry": { | |
| "type": "Polygon", | |
| "coordinates": [ | |
| [ |