gormes-parity-auditor

Audit Hermes-in-Go parity against the Python upstream with source-backed evidence.

9|Updated Apr 19, 2026

Search Tags:#compatibility #go #auditing #upstream #parity #hermes #honcho

Ready to run

npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-parity-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gormes-parity-auditor
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-parity-auditor
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-parity-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map missing Hermes-in-Go parity. This skill helps auditors identify gaps between Hermes Python upstream and Goncho-compatible Go port, generating source-backed parity evidence before builder work.

Core Features & Use Cases

Conduct comparative parity audits between Hermes in Go and the Python upstream to surface gaps.
Produce builder-ready progress rows with evidence, source refs, and actionable next steps.
Coordinate with upstream and local sources to guide refactors and feature parity planning.

Quick Start

Run the parity-auditor on the development branch to generate a source-backed parity report.

Frequently Asked Questions about gormes-parity-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit gaps in Go port parity with a Python upstream codebase?▼

To audit Go port parity with a Python upstream, you need to compare features between the branches and generate source-backed progress rows with actionable evidence. This process identifies missing functionality to guide refactoring and feature implementation.

What is the best way to track missing features between Go and Python upstream branches?▼

Tracking missing features between Go and Python upstream branches requires generating source-backed parity evidence aligned with the upstream feature map. This produces builder-ready rows that highlight compatibility gaps and corrective next steps before implementation begins.

How do I generate builder-ready parity rows with source references for a Go port?▼

Generating builder-ready parity rows with source references involves coordinating with upstream and local Go sources to compare features. The audit produces actionable evidence that aligns with the upstream feature map to drive corrective work.

When do I need to run a parity audit on my Go development branch?▼

You need to run a parity audit on your Go development branch before starting builder work to map missing Hermes-in-Go features. This generates source-backed evidence that highlights Goncho compatibility gaps and guides feature parity planning.

Can I use a parity audit to guide refactors for Goncho compatibility gaps?▼

Yes, a parity audit can guide refactors for Goncho compatibility gaps by applying comparative analysis between the Go port and Python upstream. It produces source-backed progress evidence that identifies specific areas requiring corrective implementation work.