agentleFS
Sign inStart free
InjectiveLabsInjectiveLabs/agent-skills/skills/injective-core-detect-changes/SKILL.md

injective-core-detect-changes

Skill6 starsChanged 4 months agoApache-2.0View on GitHub

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

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user inputs tags without the v prefix, e.g.

    line 29
  2. Very specific:

    Look for a heading that is ${NEXT_TAG} - YYYY-MM-DD

    line 39
  3. Distinctive:

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

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free