Prepare the repository for agent work
Make setup reproducible and supply clear conventions, repeatable guidance and validation.
Make the environment repeatable
An agent cannot reliably validate changes if the project does not build. Document dependencies, setup commands and the smallest useful tests. The infographic names copilot-setup-steps.yml; that is associated with a particular Actions-based experience, not a universal setup file for every Copilot environment.
Explain project conventions
Give concise repository instructions for architecture, naming, formatting and verification. Use more targeted guidance only when its scope is clear. Confirm the active host actually discovers it.
Package recurring procedures as skills and use focused profiles for specialized roles. Keep these sources consistent rather than copying slightly different rules into many places.
Automate objective checks
Formatting, linting and tests should provide visible evidence. Hooks can support that process, but required repository checks must still enforce merge conditions independently.
Review changes to setup scripts and hooks as executable code. Keep secrets outside committed configuration and grant only the access needed for the selected environment.
The author's recommended Cloud Agent Workshop provides hands-on practice with instructions, issue delegation and review.