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

docs(harness-ops): README skills table has no row for /harness-ops:prerequisites

Closed Beginner friendly
#9,263 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
Tech stack
markdown, shell
Domain
documentation

Research direction

Read plugins/harness-ops/README.md and check the skills table around lines 36–51 against plugins/harness-ops/skills/prerequisites/SKILL.md. Add the specified row directly after /harness-ops:check, then create the required changelog fragment and run scripts/check-changelog-fragments.sh --check and scripts/check-affected.sh --uncommitted; done means both checks pass and no other lines change.

Written by the indexing model from the issue text.

Description

pipeline-canary priority: low status: ready work-class: mechanical

Problem

plugins/harness-ops/README.md's skills table (lines 36-51) has no row for /harness-ops:prerequisites, although plugins/harness-ops/skills/prerequisites/SKILL.md exists and is user-invocable. Every other skill folder under plugins/harness-ops/skills/ has a row.

Done when

  • The table in plugins/harness-ops/README.md has one new row directly after the /harness-ops:check row, reading exactly:

    | `/harness-ops:prerequisites` | Read-only report of the external tools the enabled plugin fleet declares, and which of them are missing on this machine. Never installs. |
    
  • No other line changes, apart from one changelog fragment made with scripts/new-changelog-fragment.sh harness-ops patch (or the plugin's own release record if it is not in fragment mode).

  • scripts/check-changelog-fragments.sh --check passes.

  • scripts/check-affected.sh --uncommitted passes.

Pipeline canary

This is a deliberately tiny fix used to test the issue-to-merge pipeline end to end, first used to verify intake's verdict writer (#9213): intake should write the work class, the Size, Complexity and Uncertainty fields and a status label as the lanes App. No human in the loop: it needs no owner decision. If it stops at any stage, that stop is a pipeline defect to file, not a problem with this issue.

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

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.