Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

harness-lint

Étoiles248

Forks16

Mis à jour19 juin 2026 à 04:14

Use when working in this repository after receiving recurring coding feedback, adding or reviewing durable lint guardrails from AGENTS.md, updating rules/*.md, or finishing changes that should be checked by harness-lint.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

CorrectRoadH

CorrectRoadH/OpenTickly

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

vite-plus

CorrectRoadH/OpenTickly

Use when working in this repository and needing package management, development, build, lint, test, formatting, or JS tool execution through the Vite+ toolchain.

2026-06-19248

backend-test-worker

CorrectRoadH/OpenTickly

Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.

2026-03-25248

frontend-test-worker

CorrectRoadH/OpenTickly

Build and verify page-flow and E2E coverage for the tracking browser surface.

2026-03-25248

fullstack-regression-worker

CorrectRoadH/OpenTickly

Build cross-layer regression coverage that ties browser-visible behavior to backend truth.

2026-03-25248

test-platform-worker

CorrectRoadH/OpenTickly

Harden shared test infrastructure, runtime readiness, schema setup, and parallel lane behavior.

2026-03-25248

tracking-backend-worker

CorrectRoadH/OpenTickly

Update backend timer/time-entry contracts, regressions, and source docs for the timer refactor mission.

2026-03-25248

name	harness-lint
description	Use when working in this repository after receiving recurring coding feedback, adding or reviewing durable lint guardrails from AGENTS.md, updating rules/*.md, or finishing changes that should be checked by harness-lint.

Harness Lint

Use harness-lint to turn recurring repository feedback into executable or reviewable rules.

Workflow

Run commands from the repository root.
Use harness-lint from PATH. If it is missing on this machine and /Users/ctrdh/Code/harness-lint/target/debug/harness-lint exists, that local debug binary is an acceptable fallback.
When the user gives a recurring coding preference, create or update a rule under rules/ instead of only changing the current code.
Rules must use GritQL for executable checks. If the preference needs cross-file state, changed-file path ownership, human review, or richer semantics than a stable GritQL pattern can provide, keep it as status: draft.
Do not delete, disable, or weaken rules to make a task pass unless the user explicitly asks for that.
Before finishing code changes, run harness-lint check --changed and report any diagnostics.
Use harness-lint rule list after changing rule configuration. It prints Markdown tables; do not pass --json to rule list.

Project Sources

AGENTS.md is the source for durable repository workflow and coding constraints.
harness.toml configures local rules and external packs.
harness.lock records installed pack revisions.
.harness/ is generated cache and must stay uncommitted.