菜单
Detect breaking changes in Injective core between two tagged releases. For use in developer documentation and release notes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Optimize AI API costs for agentic trading bots. Covers Anthropic token cost tracking, web search cost management, CoinGecko/Massive.com data sourcing, shared caching strategies, and per-user cost caps. Learned from real production data showing web search inflates costs 10-17x.
Use the Injective `injectived` CLI against a chain with consistent wallet, endpoint, and gas handling. Use the CLI map and reference docs to find commands and build transactions safely.
Audit and report adherence to Injective's documentation standards
Develop EVM smart contracts and dApps on Injective
Create and operate an INJ faucet for initializing fresh Injective wallets. Sends a small amount of INJ via EVM to create on-chain accounts and provide gas for AuthZ grants. Handles the circular dependency where fresh wallets can't transact without gas but can't receive gas without an account. Pairs with injective-trading-autosign for zero-friction onboarding.
Build, review, or debug browser frontends that sign and broadcast Injective transactions with Keplr, Leap, MetaMask, CosmJS, @injectivelabs/sdk-ts, or CosmWasm execute messages. Use this whenever implementing Injective React/Vite/Next apps, wallet connect flows, swap-contract UIs, MsgExecuteContract, MsgBroadcaster, or when errors mention EthAccount, ethsecp256k1, invalid pubkey, account sequence, signer address, Keplr, Leap, or browser wallet signing.
基于 SOC 职业分类
| name | injective-core-detect-changes |
| description | Detect breaking changes in Injective core between two tagged releases. For use in developer documentation and release notes. |
| license | MIT |
| metadata | {"author":"bguiz","version":"0.0.1"} |
Goal: identify any changes upon a new release of Injective core.
Perform the following steps in sequence.
Ask the user:
PREV_TAG what is the previous version, e.g. v1.19.0NEXT_TAG what is the next version, e.g. v1.20.0If the user inputs tags without the v prefix, e.g. 1.19.0, correct it automatically
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:
NOTES_FROM_RELEASEInvoke 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}
devrel-detect-breaking-changesIf this skill is not available, run the following command to install it:
npx skills add bguiz/devrel-agent-skills --skill devrel-detect-breaking-changes
Nil