Flyai Commit Lint

Enforce conventional commit messages with semantic validation, scope checking, and automated fix suggestions for git workflows.

Security Scan

The skill's instructions and requirements are coherent with its stated purpose (commit message linting), though the SKILL.md is high-level and assumes repository access and git without declaring git as a required binary — review how it will modify hooks or rewrite history before enabling.

Purpose & 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.

Enforce conventional commit messages across your team with semantic validation, scope verification, and automated fix suggestions.

When to use

Activate this skill when:

• A user runs git commit and the message does not follow conventional commit format
• A user asks to review or fix commit messages in a branch
• Pre-commit hooks need commit message validation
• CI pipelines require commit format enforcement

Commit Format

All commits must follow the pattern: type(scope): subject

Allowed Types

Type	Description
feat	A new feature
fix	A bug fix
docs	Documentation changes
style	Formatting, missing semicolons, etc.
refactor	Code change that neither fixes a bug nor adds a feature
perf	Performance improvement
test	Adding or updating tests
chore	Maintenance tasks
ci	CI/CD configuration changes
build	Build system or dependency changes

Scope Rules

• Scope is optional but recommended
• Must be lowercase kebab-case
• Should match a module, component, or directory name in the project
• Examples: auth, api, ui, database, ci

Subject Rules

• Use imperative mood: "add feature" not "added feature"
• No period at the end
• Maximum 72 characters
• Start with lowercase

Validation Process

1. Parse the commit message into type, scope, subject, body, and footer
2. Validate type against the allowed list
3. Check scope format if present
4. Verify subject follows all rules
5. Check total first line length does not exceed 72 characters
6. If body is present, ensure blank line separator exists

Auto-Fix Suggestions

When a commit message fails validation, suggest fixes:

• Wrong type: suggest the closest matching type
• Uppercase subject: auto-lowercase the first character
• Period at end: remove trailing period
• Past tense: suggest imperative form (added -> add, fixed -> fix)
• Missing type: infer from changed files (test files -> test, docs -> docs)

Integration

Works with:

• Git hooks (pre-commit, commit-msg)
• GitHub Actions CI checks
• Local development workflow
• Branch history cleanup before merge

Examples

Good:

• feat(auth): add OAuth2 login flow
• fix(api): handle null response from upstream
• docs: update API reference for v2 endpoints
• refactor(database): extract connection pooling logic

Bad:

• Added new feature (missing type)
• feat: Add OAuth2. (uppercase, period)
• fix(API): Fixed the bug (uppercase scope, past tense)