github.com/gfx-rs/wgpu (link)

commit signals (8)

• AiCoAuthor
  Tool: claude-codeCommit: d30e2dd6d6e0d5c10f225261e5b54f96c8992cc5Authored: 2 weeks ago (Tue, 1 Sep 2026 10:47:44 +0000)Match: Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
• AiCoAuthor
  Tool: claude-codeCommit: f892b2e235752117175098d26ba7c2c6d5f5c6b3Authored: 1 month ago (Tue, 21 Jul 2026 19:05:24 +0000)Match: Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
• AiCoAuthor
  Tool: claude-codeCommit: 977e85dca6fd6d1f6edf4337f57a8653520d42fbAuthored: 2 months ago (Wed, 24 Jun 2026 15:31:48 +0000)Match: Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
• AiCoAuthor
  Tool: github-copilotCommit: 7caf9fabc37a4fc692cda6ed1618a6a71e80b5e5Authored: 6 months ago (Sun, 1 Mar 2026 11:37:26 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
• AiCoAuthor
  Tool: github-copilotCommit: 952d653835402dbff06477e1bd256dd505322e2bAuthored: 9 months ago (Wed, 17 Dec 2025 05:13:27 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
• AiCoAuthor
  Tool: github-copilotCommit: 5444e19e4f1df798b0461adf67cb61f50b3bd101Authored: 9 months ago (Mon, 15 Dec 2025 18:03:16 +0000)Match: Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
• AiCoAuthor
  Tool: github-copilotCommit: 5444e19e4f1df798b0461adf67cb61f50b3bd101Authored: 9 months ago (Mon, 15 Dec 2025 18:03:16 +0000)Match: Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
• AiCoAuthor
  Tool: github-copilotCommit: 05cc6dca82fe5f5890299abf7cde6f1cd2907a26Authored: 11 months ago (Thu, 25 Sep 2025 03:24:56 +0000)Match: Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

source signals (6)

• File: AGENTS.mdTool: agents-md

  # Global instructions
  
  ## Code Style
  
  - Limit the amount of comments you put in the code to a strict minimum. You should almost never add comments, except sometimes on non-trivial code, function definitions if the arguments aren't self-explanatory, and class definitions and their members.
  - Do not use emoji.
  
  ## Workflow
  
  - You can test that the code builds by running `cargo build`. Don't pass `--release` unless there's a specific need to test a release build, it's much slower.
  - After making code changes, 

• File: .claude/skills/webgpu-specs/SKILL.mdTool: unspecified

  ---
  name: webgpu-specs
  description: Download WebGPU and WGSL specifications for use as a reference
  allowed-tools: "Bash(sh .claude/skills/webgpu-specs/download.sh)"
  ---
  
  Run `sh .claude/skills/webgpu-specs/download.sh` to download the
  WebGPU and WGSL specifications if they are not present or if they have
  been updated. You do not need to change directory before running the script.
  
  After the specs are downloaded, you can search in `target/claude/webgpu-spec.bs`
  and `target/claude/wgsl-spec.bs` for relevant s

• File: .claude/skills/cts-triage/SKILL.mdTool: unspecified

  ---
  name: cts-triage
  description: Run CTS test suites and investigate failures
  ---
  
  # Triage Process
  
  When working on a category of CTS tests, follow this systematic process to identify issues, prioritize fixes, and document findings.
  
  ## Step 0: Divide Into Manageable Chunks
  
  List all the tests matching a selector:
  
  ```bash
  cargo xtask cts -- --list 'webgpu:api,validation,*' 2>&1 | wc -l
  ```
  
  If there is a reasonable number of tests matching the selector (less than a
  couple hundred or so, but this isn't a 

• Dir: .claudeTool: claude-code
• Dir: .claudeTool: claude-code
• Dir: .claudeTool: claude-code

ignorefile signals (0)

none