pre-push-skill
Executes the required pre-push steps for the flutter/packages repository. Call this tool immediately whenever the user asks to push, asks if the user/you are ready to push, or wants to validate their local changes are ready to become a pull request. Published by flutter in packages.
Decision snapshot
Is this a fit?
Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
11 days ago · BSD-3-Clause license
No specific cautions were detected. Review the source and requested permissions before installing.
What is pre-push-skill?
Executes the required pre-push steps for the flutter/packages repository. Call this tool immediately whenever the user asks to push, asks if the user/you are ready to push, or wants to validate their local changes are ready to become a pull request. Published by flutter in packages. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Declared skill metadata
- Source file: packages/camera/camera_android_camerax/.agents/skills/pre-push-skill/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use pre-push-skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: flutter
- Repository: flutter/packages
- Skill file: packages/camera/camera_android_camerax/.agents/skills/pre-push-skill/SKILL.md
What it does
Executes the required pre-push steps for the flutter/packages repository. Call this tool immediately whenever the user asks to push, asks if the user/you are ready to push, or wants to validate their local changes are ready to become a pull request.
Skill instructions
Pre-Push Skill Checks to Verify Prerequisites - gh (GitHub CLI) must be installed and authenticated. If not in your PATH, check common locations like /opt/homebrew/bin/gh on macOS or C:\Program Files\GitHub CLI\gh.exe on Windows. 1. Initial Clean Working Tree Check The first step is ensuring that all changes are committed and there are no tracked files with lingering non committed state. Command to run: bash git status --porcelain If this command outputs anything, then there are uncommitted git changes. The code is not ready to push. 2. Check for Changed Files You must verify that there are actually changed files to test. Command to run: bash git fetch origin main git diff --name-only origin/main...HEAD | grep '^packages/camera/cameraandroidcamerax' If this command outputs nothing, then no relevant files were modified in this branch. There is no code to push for cameraandroidcamerax, and you can skip all remaining validation steps and jump to "Take Action" where you will inform the use
Verified compatibility and discovery
Frequently asked questions
What is pre-push-skill?
pre-push-skill is a open-source AI agent skill with Copy skill directory. Executes the required pre-push steps for the flutter/packages repository. Call this tool immediately whenever the user asks to push, asks if the user/you are ready to push, or wants to validate their.
Who is pre-push-skill best for?
pre-push-skill is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install pre-push-skill?
Install or run pre-push-skill using Copy skill directory. Check pre-push-skill for the latest setup command.
Is pre-push-skill actively maintained?
pre-push-skill may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
