Flyai Commit Lint
v1.0.0Enforce conventional commit messages with semantic validation, scope checking, and automated fix suggestions for git workflows.
⭐ 0· 57·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description align with the instructions: parsing and validating commit messages, suggesting fixes, and integrating with git hooks/CI. One small inconsistency: the SKILL.md expects interaction with git (commit hooks, changed files) but the registry metadata lists no required binaries (git) — this is plausible but should be declared.
Instruction Scope
Instructions stay within commit-linting scope (parse message, suggest fixes, infer type from changed files). However, it mentions integrations that are potentially destructive (branch history cleanup, modifying commit messages) — the instructions do not spell out confirmation/approval steps before rewriting history or amending commits, so require explicit user consent or safeguards.
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install surface. Nothing is written to disk by the skill itself as provided.
Credentials
No environment variables, credentials, or external config paths are requested. The actions described (reading repo files, modifying hooks) are proportionate to the stated purpose.
Persistence & Privilege
always:false and default autonomous invocation are set; this is normal. The skill may be used to modify repository hooks or commit history when invoked, but it does not request permanent platform-wide presence.
Assessment
This skill appears to do what it says (lint and suggest fixes for commit messages). Before installing: ensure git is available on the agent, and verify exactly how the skill will modify your repository (pre-commit/commit-msg hook contents, whether it will auto-amend commits or rewrite branch history). Require explicit confirmation for any auto-amend or history-rewrite actions and keep backups (or enforce that changes run only locally/under user approval). If you plan to use it in CI, request the actual hook/automation scripts so you can review them for unintended behavior.Like a lobster shell, security has layers — review code before you run it.
latestvk970n04mtv39dsgjn5rhzvp3rn842w3b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.