find-release
- Repo stars 176,634
- Author updated Live
- Author repo flutter
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @flutter · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Env read
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: find-release
description: A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill wh…
category: ai
runtime: no special runtime
---
# find-release output preview
## PART A: Task fit
- Use case: A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill whenever users ask about when a commit landed in Flutter or Dart releases, inquire about release versions for specific SHAs, or want to know if a commit is included in stable, beta, or dev channels for Flutter/Dart projects..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Instructions / Examples” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill whenever users ask about when a commit landed in Flutter or Dart releases, inquire about release versions for specific SHAs, or want to know if a commit is included in stable, beta, or dev channels for Flutter/Dart projects.”.
- **02** When the source has headings, the agent prioritizes “Instructions / Examples” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands, read environment variables.
Validate with a small run
Start with a small task and check whether the result follows “Instructions / Examples”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: find-release
description: A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill wh…
category: ai
source: flutter/flutter
---
# find-release
## When to use
- A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill whenever users ask about…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Instructions / Examples” and keep inference separate from source facts.
- read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "find-release" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Instructions / Examples
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands, read environment variables | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review