Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🤖 verification skills: harden check.sh and verify.sh argument and file handling (#391 follow-ups)

Open Beginner friendly
  • Is something wrong?
#392 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
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash
Domain
devops, tooling

Research direction

Read hack/formal/aigatewaykey/check.sh and .mux/skills/verify-coder-k8s/scripts/verify.sh. Check how check.sh parses --config, --out, and --set, then inspect load_run and the EXIT traps in verify.sh. Done when missing option values exit 2, run.env is rejected if it is a symlink or has group/other write bits, and trap handling works with a single quote in VERIFY_RUN_DIR; no test or run command is named in the issue.

Written by the indexing model from the issue text.

Description

Follow-ups from Codex review round 4 on #391. Under the review limit for #391 (rounds 4 to 6 fix blockers only), I judged these minor and deferred them.

  1. hack/formal/aigatewaykey/check.sh: --config, --out or --set as the last argument exits 1 ("unbound variable"). Exit 1 means a rule violation. A malformed call must exit 2. Fix: check that each option has a value before reading $2.
  2. .mux/skills/verify-coder-k8s/scripts/verify.sh load_run: before it sources run.env, check that the file is a regular file (not a symlink) with no group or other write bits. Launch creates it with mode 0600 in a private run dir, so this matters only after someone changes its mode.
  3. verify.sh EXIT traps (coder-api port-forward, temp files): the traps build shell code from expanded paths. A ' in VERIFY_RUN_DIR breaks the trap and leaves the port-forward running. Use a trap function that reads already-set variables.

Trigger: the next change to either script.

Generated with mux • Model: anthropic:claude-opus-5-5 • Thinking: high

Dominant language
Go
Stars
5
Forks
3
Avg merge
2h 56m
Merged PRs (30d)
163

Getting set up

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 coder/coder-k8s

All issues in coder/coder-k8s

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.