find-release
- Repo stars 176,634
- Author repo flutter
Instructions
Extract Information:
- Identify the commit SHA from the user's request (e.g.,
02abc57). - Identify the target channel (one of:
stable,beta,dev). If not specified, try each.
- Identify the commit SHA from the user's request (e.g.,
Execute Search:
- Ensure the
find_release.darttool is available. The tool is typically located at find_release.dart relative to the Flutter workspace root. If the workspace root is not the default, set the environment variableFIND_RELEASE_TOOL_PATHto the absolute path of the tool. - Run the tool using the path to ensure it works from any directory within the workspace.
- Command:
dart run ${FIND_RELEASE_TOOL_PATH:-engine/src/flutter/third_party/dart/tools/find_release.dart} --commit=<SHA> --channel=<CHANNEL>
- Ensure the
Interpret and Report Results:
- The tool will report which repository (
dart-lang/sdkorflutter/flutter) the commit was found in. - It will provide the "Lowest release tag" (the git tag containing the commit).
- It will provide the "Lowest Flutter release" and/or "Lowest Dart release" version for the specified channel.
- Present these findings clearly to the user. If the commit is not found or not yet in a release for that channel, inform the user accordingly.
- Handle edge cases: If the SHA is invalid or not found, suggest checking the SHA. If the channel is invalid, default to stable and notify the user.
- The tool will report which repository (
Examples
User: "When did commit 02abc57 land in stable?"
Agent: Runs
dart run ${FIND_RELEASE_TOOL_PATH:-engine/src/flutter/third_party/dart/tools/find_release.dart} --commit=02abc57 --channel=stableand reports the release version.User: "Is 02abc57 in beta?"
Agent: Runs the command with
--channel=beta.
- Fluxly category
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @flutter · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Guided setup
- External API key
- No requirement detected
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Env read
- Detected network behavior
- Local-only
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. Extract Information: Identify the commit SHA from the user's request (e.g., 02abc57). Identify the target channel (one of: stable, beta, dev). If not specified, try each.
User: "When did commit 02abc57 land in stable?" Agent: Runs dart run ${FINDRELEASETOOLPATH:-engine/src/flutter/thirdparty/dart/tools/findrelease.dart} --commit=02abc57 --channel=stable and reports the release version. User: "Is 02abc57 in beta?"
## Instructions
1. **Extract Information:**
- Identify the commit SHA from the user's request (e.g., `02abc57`).
- Identify the target channel (one of: `stable`, `beta`, `dev`). If not specified, try each.
2. **Execute Search:**
- Ensure the `find_release.dart` tool is available. The tool is typically located at [find_release.dart](../../../engine/src/flutter/third_party/dart/tools/find_release.dart) relative to the Flutter workspace root. If the workspace root is not the default, set the environment variable `FIND_RELEASE_TOOL_PATH` to the absolute path of the tool.
- Run the tool using the path to ensure it works from any directory within the workspace.
- Command: `dart run ${FIND_RELEASE_TOOL_PATH:-engine/src/flutter/third_party/dart/tools/find_release.dart} --commit=<SHA> --channel=<CHANNEL>`
3. **Interpret and Report Results:**
- The tool will report which repository (`dart-lang/sdk` or `flutter/flutter`) the commit was found in.
- It will provide the "Lowest release tag" (the git tag containing the commit).
- It will provide the "Lowest Flutter release" and/or "Lowest Dart release" version for the specified channel.
- Present these findings clearly to the user. If the commit is not found or not yet in a release for that channel, inform the user accordingly.
- Handle edge cases: If the SHA is invalid or not found, suggest checking the SHA. If the channel is invalid, default to stable and notify the user.
## Examples
- **User:** "When did commit 02abc57 land in stable?"
- **Agent:** Runs `dart run ${FIND_RELEASE_TOOL_PATH:-engine/src/flutter/third_party/dart/tools/find_release.dart} --commit=02abc57 --channel=stable` and reports the release version.
- **User:** "Is 02abc57 in beta?"
… Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Instructions → Examples
terms -> Extract Information · Execute Search · Interpret and Report Results · User · Agent
files/cmd -> 02abc57 · stable · beta · dev · findrelease.dart · FINDRELEASETOOLPATH · dart-lang/sdk · flutter/flutter
body sha256 -> e0cbf9186f6f
Decide Fit First
Design Intent
How To Use It
Boundaries And Review