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

fix(ci): check-changed-skills.sh fails a stale branch on skills only main changed

Open Beginner friendly
  • Is something wrong?
#7,014 1 comment 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
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, git
Domain
build-system

Research direction

The bug is in scripts/check-changed-skills.sh: the changed set comes from changed_files::into changed_paths "$BASE" (around line 123) and the per-skill check runs git diff --name-only "$BASE" -- "$skill_dir/SKILL.md" (around line 175). Reproduce by running the script against origin/main on a branch behind main, then resolve BASE with git merge-base "$BASE" HEAD before both calls. Done when a branch behind its base no longer reports skills only main changed, and a new test covers a branch behind its base.

Written by the indexing model from the issue text.

Description

good first issue needs-triage priority: medium

Problem

Run locally as scripts/check-changed-skills.sh origin/main on a branch behind main, the script also checks skills that only main changed and fails on them.

Seen on 2026-10-10 on feat/agent-tool-spawn-effort (#6913), 44 commits behind main. It failed on plugins/harness-config/skills/audit/scripts/fix-plugin-drift.test.sh, which the branch never touched. Against the merge base (e971f640b3) it passed: "6 skill(s) checked, 0 failed."

Cause: the changed set and the per-skill diff are taken against the base ref as given. The changed set comes from changed_files::into changed_paths "$BASE" and the per-skill check from git diff --name-only "$BASE" -- "$skill_dir/SKILL.md" (scripts/check-changed-skills.sh:123, :175). That is a two-dot comparison against the working tree, so it includes main's own changes since the branch point.

Proposed next step

Resolve $BASE to git merge-base "$BASE" HEAD before computing the changed set, so the script checks only what the branch changed. Keep CHECK_SKILL_BASE_REF semantics unchanged unless they have the same problem. Add a test with a branch behind its base.

Dominant language
Shell
Stars
22
Forks
2
Avg merge
6h 10m
Merged PRs (30d)
937

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 melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.