Harness Lint
CorrectRoadH/OpenTickly
A skill your agent uses when working in this repository after receiving recurring coding feedback, adding or reviewing durable lint guardrails from AGENTS.md, updating rules/.md, or finishing…
Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…
Install Auto Harness
$ npx skills add PacificStudio/openase --skill auto-harness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PacificStudio/openase auto-harness --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/internal/builtin/skills/auto-harness .claude/skills/auto-harness && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "auto-harness" agent skill from https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harness into .claude/skills/auto-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-harness", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harnessType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PacificStudio/openase --skill auto-harness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PacificStudio/openase auto-harness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .agents/skills && cp -r skills-src/internal/builtin/skills/auto-harness .agents/skills/auto-harness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "auto-harness" agent skill from https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harness into .agents/skills/auto-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-harness", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PacificStudio/openase --skill auto-harness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PacificStudio/openase auto-harness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/internal/builtin/skills/auto-harness .cursor/skills/auto-harness && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "auto-harness" agent skill from https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harness into .cursor/skills/auto-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-harness", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PacificStudio/openase.git --path internal/builtin/skills/auto-harness--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PacificStudio/openase --skill auto-harness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PacificStudio/openase auto-harness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/internal/builtin/skills/auto-harness .gemini/skills/auto-harness && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "auto-harness" agent skill from https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harness into .gemini/skills/auto-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-harness", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PacificStudio/openase auto-harnessInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PacificStudio/openase --skill auto-harness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .github/skills && cp -r skills-src/internal/builtin/skills/auto-harness .github/skills/auto-harness && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "auto-harness" agent skill from https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harness into .github/skills/auto-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-harness", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PacificStudio/openase --skill auto-harness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PacificStudio/openase auto-harness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PacificStudio/openase.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/internal/builtin/skills/auto-harness .opencode/skills/auto-harness && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "auto-harness" agent skill from https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/auto-harness into .opencode/skills/auto-harness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-harness", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
auto-harness- GitHub stars
- 268
- Token cost
- ~1.2k tokens
- SKILL.md length
- 592 words
- Files
- 7 (incl. references)
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…
- Works in 6 steps: Build a harness map before proposing… → Load the matching reference files. → Diagnose drift as a systems problem, not… → …
- Codex needs to audit drift-prone semantics that are repeated across code
- SKILL.md covers Overview, Workflow, Operating Rules and Default Deliverable Shape
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Auto Harness is an agent skill from PacificStudio/openase. Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding, structured logging, and technical-debt tracking. Use when Codex needs to audit drift-prone semantics that are repeated across code, docs, schemas, generated artifacts, frontend/backend boundaries, or CI, then design or implement guardrails with progressive disclosure and zero-tolerance contract checks.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `agents/openai.yaml`, `references/checklist.md` and `references/fix-plan.md`).
It sits in Development, covering Test generation, Observability and Technical debt. The repository describes itself as: Ticket-Driven Automated Software Engineering. OpenASE is an all-in-one platform that turns tickets into working code — AI agents automatically pick up tickets, execute workflows… The licence is Apache-2.0.
When your agent uses it
- Codex needs to audit drift-prone semantics that are repeated across code
- Generated artifacts
- Frontend/backend boundaries
- Implement guardrails with progressive disclosure and zero-tolerance contract checks
Example prompts
- “/auto-harness”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Build a harness map before proposing fixes.
- Load the matching reference files.
- Diagnose drift as a systems problem, not a single bug.
- Prefer hard guardrails over policy prose.
- Use tests to constrain maintainability.
- Produce actionable deliverables.
What it can do on your machine
Read from SKILL.md and the folder at commit e530faf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Auto Harness loads about 1.2k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 126 tokens; SKILL.md has 592 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from PacificStudio/openase at commit e530faf, republished under its Apache-2.0 licence (© PacificStudio). 592 words, ~1,246 tokens.
Download SKILL.mdSave it as
.claude/skills/auto-harness/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- auto-harness
- description
- Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding, structured logging, and technical-debt tracking. Use when Codex needs to audit drift-prone semantics that are repeated across code, docs, schemas, generated artifacts, frontend/backend boundaries, or CI, then design or implement guardrails with progressive disclosure and zero-tolerance contract checks.
Auto Harness
Overview
Design the project harness so repository rules become executable. Start by mapping where semantics can drift, then convert the risky ones into generated artifacts, contract tests, type or layer guards, and CI checks.
Workflow
Build a harness map before proposing fixes.
- Read entrypoint materials first:
AGENTS.md, repo-root docs,Makefile, package scripts, CI workflows, API specs, codegen config, lint config, type-check config, and test runners. - Avoid bulk-loading every doc. Follow progressive disclosure: read only the references needed for the current risk.
- Record the harness surfaces that already exist: documentation rules, generated files, test suites, CI gates, architecture constraints, observability standards, and debt tracking.
- Read entrypoint materials first:
Load the matching reference files.
- Read
references/checklist.mdto score the current harness and find missing guardrails. - Read
references/guide.mdwhen you need the design principles and recommended repository shapes. - Read
references/guard-patterns.mdwhen you need concrete enforcement strategies. - Read
references/fix-plan.mdwhen you need a staged remediation plan or a deliverable template. - Read
references/upstream.mdwhen you need the builtin bundle provenance or manual sync guidance.
- Read
Diagnose drift as a systems problem, not a single bug.
- Search for the same semantic repeated across layers: permissions, routes, CLI commands, OpenAPI, generated clients, frontend assumptions, docs, logging fields, config, and tests.
- Flag any semantic that is declared in multiple places without a hard synchronization mechanism.
- Treat "scope list says yes, runtime path says no" and similar mismatches as harness failures, not just implementation bugs.
- Write the diagnosis in terms of duplicated authority, missing invariants, missing generated artifacts, or missing tests.
Prefer hard guardrails over policy prose.
- Establish a single source of truth for drift-sensitive semantics.
- Generate downstream artifacts instead of hand-maintaining parallel definitions.
- Add failing checks in CI for zero-drift contracts: OpenAPI parity, generated client freshness, import-layer guards, JSON schema checks, snapshot parity, or table-driven route or scope coverage.
- Add type-level or package-boundary checks when architecture depends on layering.
- Add structured logs when the real system is expensive to exercise and deterministic tests are limited.
Use tests to constrain maintainability.
- Add unit tests for pure rules and table-driven contracts.
- Add integration tests for boundary behavior, storage wiring, and auth or permission enforcement.
- Add e2e tests for user-visible workflows and generated frontend/backend integration points.
- Add regression tests for every bug whose root cause was semantic drift across layers.
- Favor tests that prove two layers cannot disagree, rather than tests that only validate each layer in isolation.
Produce actionable deliverables.
- Deliver a short harness map.
- Deliver the top drift risks and why they exist.
- Deliver a prioritized fix plan with fast wins, foundational changes, and CI gates.
- If asked to implement, land the smallest durable guardrail first, then expand coverage.
Show full SKILL.md (149 more words)Show less
Operating Rules
- Prefer executable constraints over narrative guidance.
- Prefer generated artifacts over duplicate handwritten definitions.
- Prefer progressive disclosure over dumping every document into context.
- Prefer contract tests that cover real commands, real routes, and real generated clients.
- Treat frontend/backend contract drift as zero-tolerance when codegen or schema generation is feasible.
- Treat missing structured logs as a harness defect when external integrations are costly to replay.
- Keep fixes incremental, but design around the final source-of-truth model.
Default Deliverable Shape
Return these sections when doing a harness audit:
Harness Map- current rules, generators, tests, CI gates, and documentation entrypoints.Drift Risks- duplicated semantics, weak invariants, or missing sync checks.Guardrail Plan- concrete code or test mechanisms that would prevent recurrence.Fix Order- what to land first, what to generate later, and what to move into CI.Residual Risks- what still depends on convention instead of enforcement.
© PacificStudio, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (references) in internal/builtin/skills/auto-harness of PacificStudio/openase.
- SKILL.md
- agents/openai.yaml
- references/checklist.md
- references/fix-plan.md
- references/guard-patterns.md
- references/guide.md
- references/upstream.md
Open the folder on GitHubat commit e530faf
Compare with similar skills
Auto Harness next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Auto Harness this skillPacificStudio/openase | 268 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Harness LintCorrectRoadH/OpenTickly | 306 | — | ~396 | Automated safety check: Pass | AGPL-3.0 | |
| Cxas Agent FoundryGoogleCloudPlatform/cxas-scrapi | 107 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Add Plugin Ruleeslint-config/airbnb-extended | 129 | — | ~646 | Automated safety check: Pass | MIT | |
| Lint Repository Markdowncodsen/codsen | 214 | — | ~832 | Automated safety check: Pass | MIT | |
| Existing Repoalinaqi/maggy | 707 | — | ~4k | Automated safety check: Notes | MIT |
Similar skills
Cxas Agent Foundry
GoogleCloudPlatform/cxas-scrapi
End-to-end GECX/CXAS/CES conversational agent lifecycle -- build agents from requirements (PRD-to-agent), create and run evals (goldens, simulations, tool tests, callback tests), debug failures, and…
Add Plugin Rule
eslint-config/airbnb-extended
Fix the "<Plugin Updated with <rule" build error from script/checkUpdates.ts by adding a new or deprecated plugin rule to the right rules/ file.
Lint Repository Markdown
codsen/codsen
Keep the repository's linted Markdown passing npm run lint:markdown.
Existing Repo
alinaqi/maggy
Analyze existing repositories, maintain structure, setup guardrails and best practices
Figma Policy Guardrails
jeremylongshore/tons-of-skills-marketplace
Enforce security policies and coding standards for Figma API integrations.
More from PacificStudio/openase
All 14 skills in this repoDeploy Coolify Review Env
PacificStudio/openase
Create or update a branch-scoped Coolify review environment with one command, and delete it with one command.
Deploy Openase
PacificStudio/openase
Build and locally redeploy OpenASE from the current branch, including web static assets and the Go binary, then restart the local service and verify health.
Local Bootstrap CLI Auth Debug
PacificStudio/openase
Diagnose and repair OpenASE CLI access in local bootstrap mode.
Push
PacificStudio/openase
Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.
Report Issue
PacificStudio/openase
Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo).
Openase Platform
PacificStudio/openase
Platform operations for tickets, projects, and runtime coordination inside OpenASE.
Related
Questions about Auto Harness
What does Auto Harness do?
Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding…. Auto Harness is an agent skill from PacificStudio/openase.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding, structured logging, and technical-debt tracking.
When should I use Auto Harness?
Auto Harness fits situations like: Codex needs to audit drift-prone semantics that are repeated across code; generated artifacts; frontend/backend boundaries; implement guardrails with progressive disclosure and zero-tolerance contract checks.
How do I install Auto Harness in Claude Code?
Run `npx skills add PacificStudio/openase --skill auto-harness -a claude-code`. Or copy the skill folder (internal/builtin/skills/auto-harness in PacificStudio/openase) into .claude/skills/auto-harness in your project. Claude Code loads it when a task matches its description.
How do I install Auto Harness in Codex?
Run `npx skills add PacificStudio/openase --skill auto-harness -a codex`. Or copy the skill folder (internal/builtin/skills/auto-harness in PacificStudio/openase) into .agents/skills/auto-harness in your project. Codex loads it when a task matches its description.
Can I use Auto Harness in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PacificStudio/openase --skill auto-harness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-harness, .gemini/skills/auto-harness, .github/skills/auto-harness and .opencode/skills/auto-harness in your project.
What does Auto Harness need to run?
SKILL.md names no scripts, command-line tools or credentials: Auto Harness is instructions for the agent only.
Does Auto Harness access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Auto Harness safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Auto Harness use?
Auto Harness is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Auto Harness use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.2k tokens, read only when the agent opens those files.
What are the alternatives to Auto Harness?
Skills that share tags, products or a category with Auto Harness: Harness Lint (CorrectRoadH/OpenTickly, 306 stars), Cxas Agent Foundry (GoogleCloudPlatform/cxas-scrapi, 107 stars), Add Plugin Rule (eslint-config/airbnb-extended, 129 stars) and Lint Repository Markdown (codsen/codsen, 214 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Auto Harness?
PacificStudio (a GitHub organization) maintains it in PacificStudio/openase, which has 268 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on August 9, 2026.
Source: PacificStudio/openase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.