solver-benchmark-mandatory-checks-before-committing-reports

Sub-skill of solver-benchmark: Mandatory Checks Before Committing Reports (+2).

5 stars

Best use case

solver-benchmark-mandatory-checks-before-committing-reports is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of solver-benchmark: Mandatory Checks Before Committing Reports (+2).

Teams using solver-benchmark-mandatory-checks-before-committing-reports should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/mandatory-checks-before-committing-reports/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/engineering/marine-offshore/solver-benchmark/mandatory-checks-before-committing-reports/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/mandatory-checks-before-committing-reports/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How solver-benchmark-mandatory-checks-before-committing-reports Compares

Feature / Agentsolver-benchmark-mandatory-checks-before-committing-reportsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of solver-benchmark: Mandatory Checks Before Committing Reports (+2).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Mandatory Checks Before Committing Reports (+2)

## Mandatory Checks Before Committing Reports


```
[ ] Master summary verdict matches individual report content
[ ] "Headings: N" shows the correct count (not 0 for cases with wave headings defined)
[ ] DOF plots contain actual data (not flat lines from empty heading arrays)
[ ] All physics sections present: hydrostatics, load RAOs, roll damping, mesh quality
[ ] Navigation links between combined report and per-body reports work
```

## Known Bug: `diff.headings` Returns Empty After `Calculate()`


**Affected cases**: `full_qtf` analysis type, certain bi-symmetric configurations, fixed-DOF bodies.

**Symptom**: Report header shows `Headings: 0 (°)` even though wave headings are
defined in spec.yml. DOF plots appear empty because heading data is missing.

**Root cause**: `OrcFxAPI.Diffraction.headings` may return an empty array after
`Calculate()` is called in memory. The property is only reliably populated after
`LoadResults()` from a saved `.owr` file.

**Workaround**: Pass the saved `.owr` path to the report generator via:

*See sub-skills for full details.*

## Regenerating Stale Reports


```bash
# Regenerate a single case (re-runs OrcaWave — takes ~30-120s)
uv run python scripts/benchmark/validate_owd_vs_spec.py --case 2.2

# Regenerate master summary only (fast — reads cached JSON, no OrcaWave run)
uv run python scripts/benchmark/validate_owd_vs_spec.py --summary-only

# Regenerate all cases (slow — runs OrcaWave for each)
uv run python scripts/benchmark/validate_owd_vs_spec.py --all
```

Related Skills

worktree-pre-push-bypass-for-tier1-checks

5
from vamseeachanta/workspace-hub

Handle workspace-hub integration-branch pushes from isolated git worktrees when the pre-push hook incorrectly assumes sibling tier-1 repos exist under the worktree path.

verify-Codex-run-commit-vs-working-tree-before-closing

5
from vamseeachanta/workspace-hub

After a Codex implementation run, verify the claimed file set against the actual commit and working tree before treating the issue as fully complete.

engineering-solver-domain-recon

5
from vamseeachanta/workspace-hub

Deep reconnaissance of an engineering solver domain (OrcaWave, OrcaFlex, CalculiX, OpenFOAM, etc.) across a multi-repo ecosystem — map infrastructure, issues, skills, data artifacts, machine constraints, and solver queue state before planning work.

orcawave-aqwa-benchmark

5
from vamseeachanta/workspace-hub

Cross-validation specialist for comparing OrcaWave and AQWA diffraction analysis results. Provides statistical comparison, peak value validation, and automated benchmark reporting for hydrodynamic coefficient verification.

core-context-management-size-limits-mandatory

5
from vamseeachanta/workspace-hub

Sub-skill of core-context-management: Size Limits (MANDATORY) (+3).

git-sync-manager-1-always-check-before-operating

5
from vamseeachanta/workspace-hub

Sub-skill of git-sync-manager: 1. Always Check Before Operating (+4).

clean-code-step-1-api-compatibility-check-mandatory-before-wr

5
from vamseeachanta/workspace-hub

Sub-skill of clean-code: Step 1: API Compatibility Check (MANDATORY before writing shims) (+2).

solver-benchmark-solver-paths

5
from vamseeachanta/workspace-hub

Sub-skill of solver-benchmark: Solver Paths.

solver-benchmark-related-work-items

5
from vamseeachanta/workspace-hub

Sub-skill of solver-benchmark: Related Work Items.

solver-benchmark-programmatic-usage

5
from vamseeachanta/workspace-hub

Sub-skill of solver-benchmark: Programmatic Usage.

solver-benchmark-pre-flight-validation-checklist

5
from vamseeachanta/workspace-hub

Sub-skill of solver-benchmark: Pre-Flight Validation Checklist.

solver-benchmark-orcawave-via-orcfxapi

5
from vamseeachanta/workspace-hub

Sub-skill of solver-benchmark: OrcaWave (via OrcFxAPI) (+3).