divedra-fix

Diagnose and fix upstream divedra integration bugs with local submodule validation.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tacogips/cursor-cli-agent --skill divedra-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: divedra-fix
Source: https://github.com/tacogips/cursor-cli-agent/tree/main/.agents/skills/divedra-fix
Command: npx skills add https://github.com/tacogips/cursor-cli-agent --skill divedra-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use this skill when a divedra workflow, CLI command, GraphQL control plane, event listener, or submodule integration appears to fail due to an upstream divedra bug. Reproducing with the local submodule, filing an upstream issue, fixing the submodule, validating it, and committing the divedra change.

Core Features & Use Cases

  • Diagnose whether the fault is in this repository's integration or in the divedra submodule.
  • Provide a workflow for submodule fixes including testing, type checks, and CI steps.
  • Coordinate upstream reporting and local validation before pushing changes.

Quick Start

Reproduce the issue with the local submodule, implement a minimal fix, and commit the changes to the submodule and the parent repository.

Frequently Asked Questions about divedra-fix

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

FAQPage Schema
How do I fix an upstream submodule integration bug in my repository?

Fix an upstream submodule integration bug by reproducing the issue locally, applying a minimal fix to the submodule, validating the changes, and updating the submodule pointer in the parent repository. This workflow ensures the upstream issue is properly diagnosed and resolved.

Why does my divedra workflow or CLI command fail during integration?

A divedra workflow or CLI command fails during integration due to an upstream bug in the divedra submodule. Diagnose the fault to determine whether the issue originates in your repository's integration or within the submodule itself before applying fixes.

What is the best way to reproduce a GraphQL control plane or event listener failure?

Reproduce a GraphQL control plane or event listener failure by running the divedra integration against the local submodule. This isolates the fault to the submodule code, allowing you to implement a minimal fix and validate it before committing the change.

How do I report and fix a divedra submodule issue locally?

Report and fix a divedra submodule issue by reproducing the failure locally, filing an upstream issue when needed, applying the fix to the submodule, running tests and type checks, and committing the validated changes to both the submodule and parent repository.

Do I need to update the submodule pointer in the parent repository after fixing an upstream bug?

You need to update the submodule pointer in the parent repository after fixing an upstream bug. Validating the submodule fix locally and committing the pointer update ensures the parent repository tracks the corrected submodule state.

Can I use this workflow to diagnose whether a fault is in my integration or the divedra submodule?

You can use this workflow to diagnose whether a fault is in your repository's integration or the divedra submodule. It coordinates upstream reporting and local validation, ensuring submodule fixes are tested with type checks and CI steps before pushing changes.