kperf
Copilot instructions22 starsChanged 16 months agoMITView on GitHub
This file provides guidance to Github Copilot when working with code in this repository. See the design.md for an overview of kperf's architecture and components. See the build.md for build instructions to compile and install kperf and runkperf. See setup.md for setup instructions on how to prepare your environment for running kperf and runkperf. See the kperf.md for instructions on how to test kperf end-to-end. See the runkperf.md for instructions how to test runkperf end-to-end.
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
Files
Github Copilot
This file provides guidance to Github Copilot when working with code in this repository.
Design
See the design.md for an overview of kperf's architecture and components.
Build
See the build.md for build instructions to compile and install kperf and runkperf.
Setup
See setup.md for setup instructions on how to prepare your environment for running kperf and runkperf.
Test
See the kperf.md for instructions on how to test kperf end-to-end.
See the runkperf.md for instructions how to test runkperf end-to-end.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.