git-best-practices

Git workflow patterns for commits, branching, PRs, and history management across heterogeneous repositories. Use when creating commits, managing branches, opening pull requests, or rewriting history. Do not use for non-git implementation tasks or repo-specific release policy decisions without repository documentation.

1.50x

Quality

96%

Does it follow best practices?

Impact

90%

1.50x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

94%

Commit Recent Changes to a Backend Service

Conventional commit format and staging discipline

Criteria

Without context

With context

Two separate commits

100%

Conventional commit type used

100%

Correct type for auth change

100%

Correct type for payments change

100%

Scoped commit messages

100%

Lowercase subject lines

100%

Imperative mood

100%

No trailing period

100%

Subject under 72 chars

100%

Explicit staging by name

100%

Status check before commit

Auth files staged together

100%

Without context: $0.3091 · 1m 7s · 22 turns · 27 in / 3,833 out tokens

With context: $0.5351 · 1m 29s · 31 turns · 34 in / 5,279 out tokens

80%

32%

Set Up a Feature Branch for User Profile Updates

Branch discovery and branch naming conventions

Criteria

Without context

With context

Branch discovery attempt

100%

Current branch checked

100%

Production branch checked

100%

Discovery results saved

75%

100%

Feature branch type prefix

100%

Ticket ID in branch name

100%

Branch name format

100%

Branch from default branch

100%

Fallback discovery used

Branch name stored

Without context: $0.4571 · 1m 41s · 27 turns · 32 in / 5,632 out tokens

With context: $0.6829 · 2m 4s · 38 turns · 295 in / 6,885 out tokens

98%

58%

Prepare a Feature Branch for Code Review

History rewriting and PR preparation

Criteria

Without context

With context

Backup branch created

100%

Reset to base branch tip

60%

100%

Clean narrative commits

100%

Conventional commit messages

100%

Byte-for-byte verification

100%

Force-with-lease used

83%

User confirmation noted

100%

PR title under 70 chars

100%

PR summary bullets

75%

100%

PR test plan checklist

50%

100%

Backup branch link in PR

100%

Without context: $0.7369 · 2m 57s · 32 turns · 39 in / 11,074 out tokens

With context: $1.0664 · 3m 39s · 45 turns · 82 in / 12,797 out tokens

Repository: NeverSight/skills_feed
Commit: 5342bca

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

Table of Contents

Commit Recent Changes to a Backend Service Set Up a Feature Branch for User Profile Updates Prepare a Feature Branch for Code Review

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.