[refactoring] [skill-extractor] Extract shared Go + Node + npm setup steps into shared/go-node-setup.md

Open Beginner friendly
  • Is something wrong?
#75,077 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, go, node.js
Domain
ci-cd, tooling

Research direction

Read the seven listed workflow files and compare their setup steps with shared/go-make.md. Create .github/workflows/shared/go-node-setup.md, replace the duplicated steps with imports while preserving workflow-specific steps, then run make recompile and review lock-file diffs. Done means the shared component is used by all seven workflows and recompilation succeeds.

Written by the indexing model from the issue text.

Description

cookie improvement refactoring shared-component
Opportunity

Seven workflows duplicate the same steps: block: actions/[email protected] (go-version-file: go.mod, cache: true), actions/[email protected] (node 24, npm cache), then npm ci in actions/setup/js and make deps-dev.

Current usage
  • avenger.md (~L92-112)
  • pr-finisher.md (~L97-112)
  • hourly-ci-cleaner.md (~L92-107)
  • tidy.md (~L55-70)
  • go-logger.md (~L136-150)
  • shared/ci-data-analysis.md (~L70-85)
  • shared/mcp/serena-go.md (~L24-35)

Partial copies also exist: Go-only in semantic-function-refactor.md, daily-workflow-security-model.md, daily-tlc-test-expert.md; Node-only in unbloat-docs.md, technical-doc-writer.md, visual-regression-checker.md. Version pins are repeated everywhere.

Proposed shared component

.github/workflows/shared/go-node-setup.md. It complements shared/go-make.md, which only provides mcp-scripts tools and no setup steps.

Estimated impact
  • Priority: High (5+ workflows, low complexity).
  • 7 workflows, about 15-20 lines saved each (100+ total).
  • Action version bumps are made in one place.
Migration plan
  1. Create shared/go-node-setup.md with the steps (Go, Node 24, npm ci, make deps-dev).
  2. Replace the inline steps in the 7 workflows with the import, keeping workflow-specific steps.
  3. Optionally add Go-only / Node-only variants.
  4. Run make recompile and review lock-file diffs.
Example usage
imports:
  - shared/go-node-setup.md
  - shared/go-make.md

Generated by 🔍 Workflow Skill Extractor · copilot · auto · ~20 AIC · ⌖ ~1 AIC · ⊞ 8K · ◷

  • expires on Nov 6, 2026, 7:43 PM UTC-08:00
Dominant language
Go
Stars
5.6k
Forks
615
Avg merge
5h 36m
Merged PRs (30d)
805

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-aw

All issues in github/gh-aw

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.