skills.rest
Turgunoff
TurgunoffCOMMUNITY
Explore all skills by this author →
GitHub

source-command-check

Runs dart analyze and scoped flutter tests on changed paths before committing.

Updated May 11, 2026
Search Tags:#testing#static analysis#pre-commit#flutter#git diff#flutter test#dart analyze
One-click install
npx skills add https://github.com/Turgunoff/mebellar_app --skill source-command-check-turgunoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-command-check
Source: https://github.com/Turgunoff/mebellar_app/tree/main/.agents/skills/source-command-check
Command: npx skills add https://github.com/Turgunoff/mebellar_app --skill source-command-check-turgunoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before committing or pushing Flutter code, developers need a fast sanity check that static analysis passes and the right tests run for the files they actually changed, without running the entire test suite every time. ## Core Features & Use Cases - Static Analysis Gate: Runs dart analyze lib/ and fails fast on errors while reporting warning counts. - Change-Scoped Testing: Inspects git status and git diff to run only the tests matching changed feature paths, such as test/customer/features/search/ for search changes. - Shared Code Safety: Falls back to the full flutter test suite when changes touch lib/shared/ or lib/core/. - Use Case: After editing the chat feature in a Flutter marketplace app, ask for a pre-commit check and get a compact report of analyzer results plus only the chat feature tests. ## Quick Start Run the source command check on my current changes before I commit.

Frequently Asked Questions about source-command-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a quick pre-commit check on Flutter code?▼

Run dart analyze on the lib/ directory first, then run flutter test only on the test paths matching your changed files. This gives fast feedback without executing the entire test suite on every commit.

How to run only the Flutter tests for changed files?▼

Use git status and git diff --name-only to identify changed paths, then map feature directories like lib/customer/features/search/ to their matching test folders. Changes to shared or core code should trigger the full flutter test run instead.

Should dart analyze warnings block a commit?▼

No, warnings do not block the commit in this workflow. The check fails fast only on analyzer errors, while warnings are counted and reported so you can decide whether to address them.

When should I run the full flutter test suite instead of scoped tests?▼

Run the full suite whenever changes touch shared code under lib/shared/ or lib/core/, since those modules can affect any feature. Scoped feature tests are sufficient only for isolated feature-directory changes.

What happens when a pre-commit Flutter test fails?▼

The check prints the failing output and stops without auto-fixing anything. You review the diff yourself to decide whether the test or the code is wrong before making changes.

Related Skills

Explore More Software Engineering Skills→
SameerG7SameerG7

aibom-test-impact-mapper

Map changed files to minimal pytest, npm, and Playwright test commands.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
morodomimorodomi
8

flutter-quality

Run dart analyze, dart format, and flutter test on Flutter projects.

Community
Advanced
agentcultureagentculture
112

run-tests

Run pytest suites in parallel with coverage and CI-style XML reports.

Official
Intermediate