SkillsAdd

injectivelabs/agent-skills

injective-core-detect-changes

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

First seen Jun 4, 2026

Installation

$ npx skills add injectivelabs/agent-skills --skill injective-core-detect-changes
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from injectivelabs/agent-skills · top by installs.

npx skills add injectivelabs/agent-skills
injective-cli 47 injective-mcp-servers 39 injective-evm-developer 38 linear-cli 34 injective-trading-autosign 31 injective-trading-market-data 30 injective-trading-account 29 injective-trading-tokens 25 injective-trading-chain-analysis 25 injective-trading-staking 23

Browse all from injectivelabs/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch master
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.0.1
LicenseMIT
More metadata
author
bguiz
version
0.0.1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,458 B
  • docs SUMMARY.md 161 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14 installs

SKILL.md

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 NEXTTAG. This is typically the same as NEXTTAG, 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 NOTESFROMRELEASE

3 - Detect breaking changes

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

/devrel-detect-breaking-changes 
REPO: [email protected]: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