Index of every page on this site: llms.txt
All skills
injectivelabs avatar

/injective-core-detect-changes

@6d68c2c
Run it yourself

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

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

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈156 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    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.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: MEDIUM · 2 issues

Signed by skilld at 6d68c2c. 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 6 months ago
metadata
{
  "author": "bguiz",
  "version": "0.0.1"
}

README badge

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