askill
git-standards

git-standardsSafety 85Repository

This skill should be used when the user asks to "commit changes", "create a PR", "push code", "check git status", or "review git history". Enforces safety checks and conventional commits.

8 stars
1.2k downloads
Updated 2/28/2026

Package Files

Loading files...
SKILL.md

<skill_doc>

Git Standards & Protocols

πŸ›‘ SAFETY CHECKS (Critical)

Tool Enforcement: Use the git_safe tool for all git operations (status, diff, log, add, commit, push).

Manual Agent Checks: Before ANY commit, scan staged files using git_safe(action: "diff", target: "--cached") for:

  • Secrets: .env, *_KEY, *_SECRET, password, token.
  • Large Files: Anything >10MB or binary files.
  • Build Artifacts: dist/, node_modules/, .DS_Store. Action: If found, UNSTAGE immediately and warn user.

πŸ“ Commit Protocol (Conventional)

Format: <type>(<scope>): <description>

TypeMeaning
featNew feature
fixBug fix
docsDocumentation only
refactorCode change (no feature/fix)
perfPerformance improvement
testAdding/fixing tests
choreBuild/auxiliary tools

Examples:

  • feat(auth): add google oauth provider
  • fix(login): handle null session token

πŸš€ PR Protocol

Title: Matches commit format. Body:

## Why
(Context/Problem)

## What
(Summary of changes)

## Verification
- [ ] Tests
- [ ] Manual Check

</skill_doc>

Install

Download ZIP
Requires askill CLI v1.0+β–Ά

AI Quality Score

58/100Analyzed 3/2/2026

A well-structured git workflow skill with strong safety checks and conventional commit guidance. Has clear trigger conditions, tags, and organized sections. However, located in a personal dotfiles repo with deeply nested path indicates internal-only use. Missing actual git command examples reduces actionability. Good content quality but limited reusability due to context.

85
75
50
65
60

Metadata

Licenseunknown
Version-
Updated2/28/2026
Publisherjoncrangle

Tags

ci-cdsecuritytesting