Making AI reviews useful in pull requests
AI code review becomes noisy quickly on busy pull requests. These are the patterns I would use for managed comments, finding identity, severity, evidence and merge gates.
Building better platforms with Azure, GitHub, Terraform and AI
AI code review becomes noisy quickly on busy pull requests. These are the patterns I would use for managed comments, finding identity, severity, evidence and merge gates.
Measuring AI-assisted engineering by activity alone misses the point. Active users, token usage, generated lines of code, and agent sessions are useful signals, but they do not tell you whether the work was reviewable, trusted, safe, or worth the cost.
This post looks at what platform teams should measure instead: workflow success, review effort, guardrail failures, context reuse, cost per useful outcome, and developer confidence.
The Draw.io MCP Diagramming Agent Skill provides a reusable working method for creating clear, editable diagrams with Draw.io MCP. It supports cloud architectures, network topologies, CI/CD pipelines, Kubernetes platforms, event-driven systems, C4, UML and more, while applying consistent guidance for layout, containment, connector routing, labels and validation.
Agent skills are only useful if the agent knows when to use them. A clear description acts as selection metadata, helping the agent load the right guidance, avoid noisy context, and produce more consistent results across repeated engineering tasks.
Agent skills, custom instructions, and MCP configuration are becoming part of the engineering trust boundary. This post walks through using NVIDIA SkillSpector in GitHub Actions to scan AI skill repositories, surface findings in SARIF or PR comments, and make risky agent behaviour visible during normal review.
After building a growing set of GitHub Copilot skills across areas such as Azure API Management, infrastructure as code authoring, and diagram generation with tools like Excalidraw and Draw.io, I have found that the difference between a skill that is genuinely useful and one that quietly disappoints usually comes down to a small number of … Read more