Add Copilot instructions for efficient onboarding

[Copilot]

• Explore the repository structure, documentation, build system, and workflows
• Run build and tests to understand the project behavior
• Document findings about build, test, and validation steps
• Create comprehensive .github/copilot-instructions.md file with:
  • High-level repository summary and technologies
  • Build, test, and validation instructions with verified commands
  • Project layout and architecture details
  • Key configuration files and their locations
  • CI/CD workflow information
  • Common gotchas and workarounds
• Verify the instructions file is concise (171 lines, 852 words, ~1.5-2 pages)

Summary

Created .github/copilot-instructions.md with comprehensive repository onboarding information:

Key sections included:

1. Repository overview - Tech stack (Java 21+, Spring Boot 3.5, Gradle, WebFlux, Netty, Tomcat)
2. Critical build requirements - Java 21+ requirement with setup commands, common build issues
3. Build & test commands - Verified working commands with timing information
4. Project structure - Core packages, config files, scripts, scenarios
5. CI/CD workflows - build.yaml, benchmark.yaml with verification steps
6. Benchmarking locally - Prerequisites, system tuning, execution commands
7. Testing details - 153 Java tests, Python tests, known issues
8. Key concepts - Approaches explained, delay simulation, client implementations
9. Pre-commit validation - Exact commands to verify changes
10. Common issues - Table of problems with causes and fixes
11. Making changes - Guidelines for dependencies, endpoints, scenarios

All commands verified by running:

• Build with Java 21 (successful in ~2m 25s, 153 tests passed)
• Validated Java version requirements
• Checked directory structure, config files, workflows
• Identified common issues (Java version mismatch most critical)

Original prompt

Your task is to "onboard" this repository to Copilot coding agent by adding a .github/copilot-instructions.md file in the repository that contains information describing how a coding agent seeing it for the first time can work most efficiently.

You will do this task only one time per repository and doing a good job can SIGNIFICANTLY improve the quality of the agent's work, so take your time, think carefully, and search thoroughly before writing the instructions.

- Reduce the likelihood of a coding agent pull request getting rejected by the user due to generating code that fails the continuous integration build, fails a validation pipeline, or having misbehavior. - Minimize bash command and build failures. - Allow the agent to complete its task more quickly by minimizing the need for exploration using grep, find, str_replace_editor, and code search tools. - Instructions must be no longer than 2 pages. - Instructions must not be task specific.

Add the following high level details about the codebase to reduce the amount of searching the agent has to do to understand the codebase each time:

• A summary of what the repository does.
• High level repository information, such as the size of the repo, the type of the project, the languages, frameworks, or target runtimes in use.

Add information about how to build and validate changes so the agent does not need to search and find it each time.

• For each of bootstrap, build, test, run, lint, and any other scripted step, document the sequence of steps to take to run it successfully as well as the versions of any runtime or build tools used.
• Each command should be validated by running it to ensure that it works correctly as well as any preconditions and postconditions.
• Try cleaning the repo and environment and running commands in different orders and document errors and and misbehavior observed as well as any steps used to mitigate the problem.
• Run the tests and document the order of steps required to run the tests.
• Make a change to the codebase. Document any unexpected build issues as well as the workarounds.
• Document environment setup steps that seem optional but that you have validated are actually required.
• Document the time required for commands that failed due to timing out.
• When you find a sequence of commands that work for a particular purpose, document them in detail.
• Use language to indicate when something should always be done. For example: "always run npm install before building".
• Record any validation steps from documentation.

List key facts about the layout and architecture of the codebase to help the agent find where to make changes with minimal searching.

• A description of the major architectural elements of the project, including the relative paths to the main project files, the location
  of configuration files for linting, compilation, testing, and preferences.
• A description of the checks run prior to check in, including any GitHub workflows, continuous integration builds, or other validation pipelines.
• Document the steps so that the agent can replicate these itself.
• Any explicit validation steps that the agent can consider to have further confidence in its changes.
• Dependencies that aren't obvious from the layout or file structure.
• Finally, fill in any remaining space with detailed lists of the following, in order of priority: the list of files in the repo root, the
  contents of the README, the contents of any key source files, the list of files in the next level down of directories, giving priority to the more structurally important and snippets of code from key source files, such as the one containing the main method.

- Perform a comprehensive inventory of the codebase. Search for and view: - README.md, CONTRIBUTING.md, and all other documentation files. - Search the codebase for build steps and indications of workarounds like 'HACK', 'TODO', etc. - All scripts, particularly those pertaining to build and repo or environment setup. - All build and actions pipelines. - All project files. - All configuration and linting files. - For each file: - think: are the contents or the existence of the file information that the coding agent will need to implement, build, test, validate, or demo a code change? - If yes: - Document the command or information in detail. - Explicitly indicate which commands work and which do not and the order in which commands should be run. - Document any errors encountered as well as the steps taken to workaround them. - Document any other steps or information that the agent can use to reduce time spent exploring or trying and failing to run bash commands. - Finally, explicitly instruct the agent to trust the instructions and only perform a search if the information in the instruction...

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull Request Overview

This PR adds comprehensive GitHub Copilot instructions for the loom-webflux-benchmarks repository. The document provides essential context for AI-assisted development, including repository structure, build requirements, testing procedures, and benchmarking workflows.

• Adds detailed build and test instructions with Java 21+ requirements
• Documents four tested approaches (platform-tomcat, loom-tomcat, loom-netty, webflux-netty)
• Includes CI/CD workflows, benchmarking procedures, and common troubleshooting guidance

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.