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

docs(upstream): humanlayer-skills License paragraph says notice is reproduced below but it sits above

Open Beginner friendly
#7,019 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Start in docs/upstream/humanlayer-skills.md, lines 165-166, where the rpi section's License paragraph says "reproduced below". Check the ## License notice section at lines 77-105 to confirm the MIT text is above, not below. Replace the phrase with a reference to that section by name. Done when the paragraph points readers to the License notice section and nothing else in the file changes.

Written by the indexing model from the issue text.

Description

good first issue needs-triage priority: low

What was observed

In docs/upstream/humanlayer-skills.md, the rpi section's License paragraph (line 165-166) says the repository LICENSE is "the MIT notice reproduced below". The MIT notice is not below it: it sits earlier in the file, in the ## License notice section (lines 77-105), and nothing after line 166 reproduces it. Verified on main.

Evidence

  • docs/upstream/humanlayer-skills.md:165-166 ("reproduced below")
  • docs/upstream/humanlayer-skills.md:77-105 (the notice text, under ## License notice)
  • Introduced by #6950.

Suggested fix

Change "reproduced below" to point at the section by name ("the MIT notice recorded under License notice").

Why it was not fixed in the originating PR

Found after #6950 merged, while working on unrelated items; a one-line docs fix outside that PR's scope.

🤖 Generated with Claude Code

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.