Content by Hidde de Smet's Blog (3)

Hidde de Smet lays out a practical way to judge whether a repo is actually ready for AI coding agents, using GitHub Copilot cloud agent as the concrete example. It focuses on repeatable setup, shared commands, focused tests, CI enforcement, and security boundaries so agent sessions aren’t wasted on missing prerequisites.

Hidde de Smet's Blog breaks down the difference between AGENTS.md (repo-wide, always-on instructions for coding agents) and .agent.md (custom agent profiles for GitHub Copilot), including where to place each file, what fields matter, and how to use roles, tool restrictions, and handoffs safely.

Hidde de Smet's Blog explains how GitHub Copilot “skills” work via SKILL.md folders, why the YAML description is the key to discovery, and how this approach keeps context lightweight compared to a giant copilot-instructions.md. It includes a practical Azure Monitor/Application Insights KQL skill you can copy into a repo.