All skills
injectivelabs avatar

/injective-core-detect-changes

@3e472e3

Detect breaking changes in Injective core between two tagged releases. For use in developer documentation and release notes.

Use this Skill: https://skilld.dev/gh/injectivelabs/agent-skills/injective-core-detect-changes

This session only. Nothing lands on disk.

SKILL.md

≈39 tokens always: the name and description. ≈554 when used: this file.

Detect Breaking Changes for Injective Core, Skill Guide

Goal: identify any changes upon a new release of Injective core.

When to apply

  • "Are there any breaking changes in the latest release of injectived or peggo?"
  • "For Injective Mainnet validators upgrading to vX.Y.Z, do we need extra requirements?"

Activities

Perform the following steps in sequence.

1 - Inputs

Ask the user:

  • PREV_TAG what is the previous version, e.g. v1.19.0
  • NEXT_TAG what is the next version, e.g. v1.20.0

If the user inputs tags without the v prefix, e.g. 1.19.0, correct it automatically

2 - Github info

Find the release notes for NEXT_TAG. e.g. For v1.20.0: https://github.com/InjectiveLabs/injective-core/releases/tag/v1.20.0

Find the appropriate changelog for NEXT_TAG. This is typically the same as NEXT_TAG, but swap the patch number for x. e.g. For v1.20.0: https://github.com/InjectiveLabs/injective-core/blob/release/v1.20.x/CHANGELOG.md Look for a heading that is ${NEXT_TAG} - YYYY-MM-DD

With this info:

  • Analyse them to detect any signs of potential breaking changes
  • Summarise these signs as NOTES_FROM_RELEASE

3 - Detect breaking changes

Invoke the devrel-detect-breaking-changes agent skill.

/devrel-detect-breaking-changes 
REPO: git@github.com:InjectiveFoundation/injective-core.git
PREV_TAG: ${PREV_TAG}
NEXT_TAG: ${NEXT_TAG}

PERSONAS: DevOps team running Injective mainnet validator nodes, software engineers running Injective testnet validator nodes, security team

REQS: Hint - when the following files/ globs have been changed, they are more likely to result in breaking changes:
  - `go.mod`
  - `client/docs/swagger-ui/swagger.yaml`
  - `cmd/injectived/root.go`
  - `proto/**/*.proto`
  - `injective-chain/app/app.go`
  - `injective-chain/app/**/` (when new subdirectory has been added)
Additionally, based on the release notes and change logs,
look into: ${NOTES_FROM_RELEASE}

Related skills

  • devrel-detect-breaking-changes

If this skill is not available, run the following command to install it:

npx skills add bguiz/devrel-agent-skills --skill devrel-detect-breaking-changes 

Prerequisites

Nil

Source: SKILL.md on GitHub

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill automates the process of identifying breaking changes in Injective core releases by fetching data from GitHub and utilizing a secondary helper skill. It operates as intended for developer documentation and release note preparation.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 2 issues

Signed by skilld at 3e472e3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 4 months ago
metadata
{
  "author": "bguiz",
  "version": "0.0.1"
}

README badge

README badge for injectivelabs/agent-skills/injective-core-detect-changes