agentsclimarketplace

Harness pr

Skill cekrauseee/harness/skills/harness-pr

File-native project continuity and engineering standards for coding agents.

Install
npx -y skills add cekrauseee/harness --skill harness-pr

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Draft and validate English pull requests with Conventional Commit titles and evidence-based descriptions, and publish only with explicit authorization. Use when preparing, reviewing, validating, opening, or updating a pull request.

SKILL.md

2.4 KB, 455 tokens by cl100k_base, as published. Nobody here has run it

Harness Pull Request

Derive a truthful pull request title and body from the actual diff. Drafting is read-only; opening, updating, or publishing a pull request requires explicit authorization.

Draft a Pull Request

  1. Read applicable repository instructions and identify the intended base branch.

  2. Inspect the complete diff against that base, the included commits, and relevant verification output. Do not rely on the conversation alone.

  3. Choose the primary Conventional Commit type and optional stable scope. Read references/pull-requests.md for the title and body rules.

  4. Render a standard body:

    python3 scripts/render_pr.py \
  --title "docs(harness): define artifact routing" \
  --summary "Define where final user-facing HTML artifacts belong." \
  --change "Route final HTML files to docs/artifacts/." \
  --verification "Ran python3 -m unittest discover -s tests." \
  --risk "Existing project artifacts are not migrated."

  5. Compare every statement with the diff and verification evidence. State unrun checks explicitly with a reason.

  6. Return the draft when publication is not explicitly authorized.

  7. Open or update the pull request only when explicitly requested. Re-read the remote result and report its URL.

Required Shape

The title follows the same format as a Conventional Commit so a squash merge can reuse it:

<type>(<optional-scope>)<optional-!>: <imperative English description>

The body contains exactly these sections:

## Summary

## Changes

## Verification

## Risks

Use concise English and describe the resulting change rather than the work session. Never claim tests, review, compatibility, migration, or safety that was not verified.

Authorization Boundary

  • A request to draft, validate, or review a pull request is not authorization to publish it.
  • Publishing includes draft pull requests, updates to existing pull requests, labels, reviewers, comments, and ready-for-review state.
  • A request to publish a pull request is not authorization to merge it.
  • Do not push a branch unless the user authorized the push required for publication.

What ships with it: 3 files

4.7 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.