git

Git workflow conventions for Graph Explorer. Use when making commits, creating branches, or discussing version control practices.

1.08x

Quality

81%

Does it follow best practices?

Impact

100%

1.08x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

Commit Message Cleanup

Commit message conventions

Criteria

Without context

With context

No feat/feature prefix

100%

No fix prefix

100%

No chore prefix

100%

No refactor prefix

100%

No other conventional prefixes

100%

No branch-style messages

100%

Messages are brief

100%

Messages remain descriptive

100%

Developer Onboarding: Version Control Guide

Branching strategy guide

Criteria

Without context

With context

Main as trunk

100%

Main always releasable

100%

No long-lived parallel branches

100%

No branch name prefixes

100%

No conventional commit format

100%

Atomic commits

100%

Brief descriptive messages

100%

24%

Plan Commits for a New Graph Statistics Panel

Atomic commit planning

Criteria

Without context

With context

No feat/feature prefix

100%

No fix prefix

100%

No chore prefix

100%

No refactor prefix

100%

No other conventional prefixes

100%

Atomic commits

80%

100%

Brief messages

100%

Descriptive messages

100%

Repository: aws/graph-explorer
Commit: 30587b0

Evaluated: 5 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Commit Message Cleanup Developer Onboarding: Version Control Guide Plan Commits for a New Graph Statistics Panel

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.