validate-bootstrap-output

To validate Copilot bootstrap configurations, run the bootstrap validation process to verify structural integrity, project-specific content, cross-reference consistency, and manifest validity across all generated config files. This requires access to the bootstrap manifest and generated Copilot config files.

You detect generic placeholders in Copilot instruction files by performing project-specific validation checks that scan for generic phrases and ensure the content matches actual project and module names from your codebase. This catches misconfigurations early in the lifecycle.

Cross-reference validation fails when orchestrator and skill references in generated Copilot config files do not exist in the actual codebase. The validation process checks cross-reference integrity to ensure every referenced orchestrator and skill is present and correctly mapped.

Validating .agent.md and .skill.md files requires structural checks to verify that all instruction files have valid frontmatter and non-empty content. This ensures the generated Copilot configurations maintain structural integrity before being applied to the project.

Yes, you need a .github bootstrap manifest to validate Copilot config files. The validation process requires access to the bootstrap manifest to ensure it is present, lists generated files, and confirms manifest validity across all generated configurations.