cboyd0319/HarnessForge

Create, assess, and safely update AI coding-agent repo harnesses.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jun 26, 2026
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: cboyd0319/harnessforge@cc2b48e15cb64256fd8df0defab9d7d04601c9a9 # no releases — HEAD as of 2026-07-11

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
commandCommand to run: audit, init, update, sync, verify, report, release-check, finalize-review, migrate-state, or doctor.noaudit
targetRepository path to inspect or modify.no.
python-versionPython version for the action runtime.no3.13.14
min-scoreMinimum acceptable audit score from 0 to 100.no85
fail-on-scoreFail when the audit score is below min-score.notrue
applyApply safe missing-file corrections for update, review finalization for finalize-review, or state migration for migrate-state.nofalse
forceAllow overwriting generated files during init or update.nofalse
enhance-existingAppend reviewed HarnessForge guidance to existing instruction files during init or update.nofalse
agent-fileRoot agent instruction file name to generate.noAGENTS.md
platform-contractGenerated harness platform contract.nocross-platform
with-ci-workflowAlso scaffold the optional manual HarnessForge CI workflow for init or update.nofalse
generation-max-filesMaximum number of repository files to scan during command init or applied command update.no4000
generation-component-limitMaximum number of detected components to include during command init or applied command update.no80
verify-runExecute verification checks when command is verify. Default verify mode is read-only plan mode.nofalse
verify-commandOptional newline-separated repo-owned verification commands for command verify.no""
verify-timeout-secondsPer-command timeout in seconds when command is verify and verify-run is true.no300
verify-summaryOptional target-relative compact verify evidence JSON path for command verify.no""
require-verify-evidenceRequire current passed stored verify evidence when command is sync or report.nofalse
sync-commandOptional newline-separated repo-owned readiness commands for command sync.no""
report-commandOptional newline-separated repo-owned readiness commands for command report, release-check, or finalize-review.no""
report-max-filesMaximum number of repository files to include in command report index summary.no4000
report-component-limitMaximum number of detected components to include in command report or release-check index summary.no80
report-sinceOptional git ref for command report docs fan-out analysis.no""
require-docs-fanout-budgetFail command report when docs fan-out exceeds the configured budget or duplicate durable fact blocks are present.nofalse
require-sbomFail command release-check when no existing SPDX or CycloneDX SBOM is detected.nofalse
accept-detected-high-riskRecord accepted advisory evidence for detected high-risk surfaces when command is finalize-review.nofalse
reviewed-byOptional newline-separated reviewer names for command finalize-review.no""
evidence-refOptional newline-separated evidence references for command finalize-review.no""
html-reportOptional target-relative path for an HTML audit report.no""
json-reportOptional target-relative path for an audit, sync, verify, report, release-check, finalize-review, or migrate-state JSON report.no""
markdown-reportOptional target-relative path for a Markdown report when command is report or release-check.no""
namedescription
overall-scoreHarness audit score from 0 to 100.
bottleneckLowest-scoring harness domain.
report-jsonJSON report path when requested.
report-htmlHTML report path when requested.
report-markdownMarkdown report path when requested.
changed-filesNumber of files written by init, update, finalize-review, or migrate-state.
verify-verdictVerify verdict when command is verify.
verify-summaryCompact verify evidence JSON path when requested.
readiness-verdictReadiness verdict when command is sync.
sync-exit-codeSync readiness exit code when command is sync.
docs-fanout-verdictDocs fan-out verdict when command is report or release-check.
release-verdictRelease-check verdict when command is release-check.