Answer: Use the Copilot prompt "Optimize this code for performance" to refactor code for performance optimization. Status: Confirmed Entry: tool/github-copilot/features/refactor-for-performance-optimization Revision: 3 Digest: sha256:7b19cd1fbdb2178c (changes whenever the content changes) Timeline: Created: 2026-11-13T03:33:42Z Last changed: 2026-11-18T13:12:20Z (target prime count: 10000 → —) Last verified: 2026-11-20T13:15:48Z Next check: 2026-11-21T13:15:48Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of prompt | Optimize this code for performance | [1] | 2026-11-20 Sources: [1] GitHub. "Refactoring for performance optimization - GitHub Docs". https://docs.github.com/en/copilot/tutorials/copilot-cookbook/refactor-code/refactor-for-optimization Role: primary. Accessed: 2026-11-20T13:15:48Z Quote: "Copilot prompt Optimize this code for performance" (Supports: prompt) Snapshot SHA-256: 30c905aeddd64d175a9f42137188002d6b87300b65270763436981a92810253e (captured 2026-11-18T13:12:20Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:12:20Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:15:48Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:15:48Z Last attempt: 2026-11-20T13:15:48Z Notes and limitations: Extracted automatically from a single official source (section "Example prompt"). Related: https://latestn.com/tool/github-copilot/features/refactor-readability-maintainability How do I use GitHub Copilot to refactor code for better readability and maintainability? https://latestn.com/tool/github-copilot/features/release-stages What are the release stages for GitHub Copilot features? https://latestn.com/tool/github-copilot/features/reliability-maintainability-coverage-checks How do I add reliability, maintainability, and coverage checks to GitHub Copilot reviews? https://latestn.com/tool/github-copilot/features/refactor-cross-cutting-concerns-prompt How do I use GitHub Copilot to refactor code that handles cross-cutting concerns like logging? https://latestn.com/tool/github-copilot/features/refactor-data-access-layer-prompts What example prompts can I use with GitHub Copilot to refactor a data access layer? https://latestn.com/tool/github-copilot/features/refactor-data-access-layer-response What does a GitHub Copilot response look like when refactoring a data access layer? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:12:20Z | changed | target prime count: 10000 → — | [1] 2026-11-18T13:12:20Z | changed | sample code function: is_prime → — | [1] 2026-11-16T13:00:19Z | changed | target prime count: — → 10000 | [1] 2026-11-16T13:00:19Z | changed | sample code function: — → is_prime | [1] 2026-11-16T13:00:19Z | changed | prompt: — → Optimize this code for performance | [1] 2026-11-16T13:00:19Z | changed | Sample function: every_1000th_prime → — | [1] 2026-11-16T13:00:19Z | changed | Sample code language: import time → — | [1] 2026-11-16T13:00:19Z | changed | Example prompt: Optimize this code for performance → — | [1] 2026-11-13T03:33:42Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/features/refactor-for-performance-optimization/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/features/refactor-for-performance-optimization POST: https://latestn.com/dispute/tool/github-copilot/features/refactor-for-performance-optimization with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/features/refactor-for-performance-optimization?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I use GitHub Copilot to refactor code for performance optimization? Revision 3, last verified 2026-11-20T13:15:48Z. https://latestn.com/tool/github-copilot/features/refactor-for-performance-optimization (accessed 2026-11-21T09:50:38Z). @misc{LatestN_tool_github_copilot_features_refactor_for_performance_optimization_r3, title = {How do I use GitHub Copilot to refactor code for performance optimization?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/features/refactor-for-performance-optimization}}, note = {Revision 3; digest sha256:7b19cd1fbdb2178c; last verified 2026-11-20T13:15:48Z; accessed 2026-11-21T09:50:38Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/features/refactor-for-performance-optimization