Answer: Open the project workspace in VS Code or Visual Studio and enter the prompt "@workspace Refactor this project by using AOP to avoid logging that has cross-cutting concerns" in the Copilot Chat view. The @workspace participant gives Copilot context about all the code in your workspace; in a JetBrains IDE, use @project rather than @workspace. Status: Confirmed Entry: tool/github-copilot/features/refactor-cross-cutting-concerns-prompt Revision: 3 Digest: sha256:1599b1f738ef1bdf (changes whenever the content changes) Timeline: Created: 2026-11-13T03:33:35Z Last changed: 2026-11-19T13:09:20Z (chat participant: — → @workspace) Last verified: 2026-11-20T13:15:40Z Next check: 2026-11-21T13:15:40Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of prompt | @workspace Refactor this project by using AOP to avoid logging that has cross-cutting concerns | [1] | 2026-11-20 IDE | VS Code or Visual Studio | [1] | 2026-11-20 chat participant | @workspace | [1] | 2026-11-20 JetBrains alternative | @project | [1] | 2026-11-20 Sources: [1] GitHub. "Handling cross-cutting concerns - GitHub Docs". https://docs.github.com/en/copilot/tutorials/copilot-cookbook/refactor-code/handle-cross-cutting Role: primary. Accessed: 2026-11-20T13:15:40Z Quote: "@workspace Refactor this project by using AOP to avoid logging that has cross-cutting concerns" (Supports: prompt) Quote: "Open the project workspace in VS Code or Visual Studio and enter the following prompt in the Copilot Chat view." (Supports: IDE) Quote: "The @workspace chat participant in VS Code and Visual Studio provides Copilot with context about all of the code in your workspace." (Supports: chat participant) Quote: "If you're using a JetBrains IDE, use @project rather than @workspace ." (Supports: JetBrains alternative) Snapshot SHA-256: f8f9ab418aa65c7c0373f93056b4ee8e9e662837adb674f1cb17f535803a9a95 (captured 2026-11-18T13:12:12Z) 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:11Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:15:40Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:15:40Z Last attempt: 2026-11-20T13:15:40Z Notes and limitations: Extracted automatically from a single official source (section "Example prompt"). Related: 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/github-copilot/features/refactor-for-performance-optimization How do I use GitHub Copilot to refactor code for performance optimization? https://latestn.com/tool/github-copilot/features/readme-generator-prompt-overview What does the GitHub Copilot README generator prompt do? https://latestn.com/tool/github-copilot/features/reduce-nested-logic How can GitHub Copilot help reduce nested logic in my code? https://latestn.com/tool/github-copilot/features/reduce-security-debt How can GitHub Copilot help reduce security debt in my company? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T13:09:20Z | changed | chat participant: — → @workspace | [1] 2026-11-19T13:09:20Z | changed | chat view: Copilot Chat view → — | [1] 2026-11-17T13:35:45Z | changed | chat view: — → Copilot Chat view | [1] 2026-11-17T13:35:45Z | changed | chat participant: @workspace → — | [1] 2026-11-13T03:33:35Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/features/refactor-cross-cutting-concerns-prompt/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-cross-cutting-concerns-prompt POST: https://latestn.com/dispute/tool/github-copilot/features/refactor-cross-cutting-concerns-prompt with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/features/refactor-cross-cutting-concerns-prompt?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I use GitHub Copilot to refactor code that handles cross-cutting concerns like logging? Revision 3, last verified 2026-11-20T13:15:40Z. https://latestn.com/tool/github-copilot/features/refactor-cross-cutting-concerns-prompt (accessed 2026-11-21T10:00:36Z). @misc{LatestN_tool_github_copilot_features_refactor_cross_cutting_concerns_prompt_r3, title = {How do I use GitHub Copilot to refactor code that handles cross-cutting concerns like logging?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/features/refactor-cross-cutting-concerns-prompt}}, note = {Revision 3; digest sha256:1599b1f738ef1bdf; last verified 2026-11-20T13:15:40Z; accessed 2026-11-21T10:00:36Z} } 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-cross-cutting-concerns-prompt