[deep-report] Document undocumented WASM stub files (_wasm.go) and fix stale skill doc scope
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 541
- Avg merge
- 5h 48m
- Merged PRs (30d)
- 773
Description
### Description
The WASM build-variant stub files (27 `_wasm.go` files across 6 packages: `pkg/console`, `pkg/workflow`, `pkg/parser`, `pkg/colorwriter`, `pkg/tty`, `pkg/styles`) are 81% undocumented (59 of 73 exported func/type declarations lack a doc comment), versus a 9.1% undocumented rate for the rest of the non-test Go codebase. `pkg/console` is the worst offender — live-verified: `console_wasm.go` has 32 exported func/type declarations and only 1 doc comment. Separately, `.github/skills/developer-code-organization/SKILL.md`'s "WASM Build-Variant Pattern" section is stale — it says "Seven files in `pkg/workflow/`" carry the pattern, but there are actually 27 files spanning 6 packages. Flagged in the 2026-09-15 Repository Quality Improvement Report.
### Expected Impact
Reduces risk that future contributors mis-scope new WASM stubs or violate the doc-comment convention used everywhere else in the codebase; corrects a skill doc that currently undersells the scope of the pattern by ~4x.
### Suggested Fix
1. Add doc comments to exported declarations in `pkg/console/*_wasm.go`, starting with `console_wasm.go` (highest-traffic, worst-documented file).
2. Update `.github/skills/developer-code-organization/SKILL.md`'s WASM section to reflect the actual 27-file/6-package scope, and add a short "Documentation Convention for Stubs" subsection with a one-line doc-comment template for future stub additions.
### Suggested Agent
New Agent (Go doc-comment pass) or code-simplifier
### Estimated Effort
Medium (1-4 hours)
### Data Source
DeepReport Intelligence Briefing analysis, 2026-09-15 cycle 3 — derived from Repository Quality Improvement Report - WASM Build-Variant Documentation & Stub-Coverage Debt (#61142)
> [!WARNING]
>
> Firewall blocked 1 domain
>
> The following domain was blocked by the firewall during workflow execution:
>
> - `api.anthropic.com`
>
> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter:
>
> ```yaml
> network:
> allowed:
> - defaults
> - "api.anthropic.com"
> ```
>
> See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information.
>
>
> Generated by [🔬 Deep Report](https://github.com/github/gh-aw/actions/runs/35007359021) · claude · agent · 221.8 AIC · ⌖ 11.2 AIC · ⊞ 12.8K · [◷](https://github.com/search?q=repo%3Agithub%2Fgh-aw+is%3Aissue+%22gh-aw-workflow-call-id%3A+github%2Fgh-aw%2Fdeep-report%22&type=issues)
> - [x] expires on Sep 17, 2026, 10:41 AM UTC-08:00
Contributor guide
Research direction
Start with the exported declarations in pkg/console/console_wasm.go, then compare the other _wasm.go files in pkg/console, pkg/workflow, pkg/parser, pkg/colorwriter, pkg/tty, and pkg/styles. Read the WASM Build-Variant Pattern section in .github/skills/developer-code-organization/SKILL.md; done means the targeted stubs have doc comments and the section accurately covers all 27 files and six packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- Half a day
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100