Ainative Git Workflow

Git commit, PR, and branching standards with ZERO TOLERANCE for AI attribution. Use when (1) Creating commits, (2) Writing commit messages, (3) Creating pull...

Security Scan

The skill is an instruction-only Git/PR workflow that coherently describes branch/PR/commit standards and provides hooks/commands to detect and remove AI attribution; it requests no credentials or installs and its actions align with its stated purpose.

Purpose & Capability

Name and description (git/PR/branch standards with no AI attribution) match the provided files: SKILL.md plus reference docs. There are no unrelated env vars, binaries, or external services requested.

Instruction Scope

Instructions stay within Git/PR workflow scope. They include a commit-msg hook, grep-based detection, git log checks, and guidance to amend/rebase commits and force-push to remove forbidden text. Those actions are relevant but can be operationally disruptive (history rewriting, force pushes) and should be used carefully in collaborative repositories.

Install Mechanism

Instruction-only skill with no install spec and no external downloads or packaging. Nothing will be written by an installer beyond optional git hook installation per the docs.

Credentials

No required environment variables, credentials, or config paths are requested. The skill uses only local git commands and repository files, consistent with its purpose.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. It recommends installing a local .git/hooks/commit-msg hook which modifies repository files and enforces checks locally—this is expected but should be deployed with team agreement because it affects commit flow.

Assessment

This skill is internally consistent and does what it says: enforce no-AI-attribution and provide branch/PR templates and a commit hook. Before installing: (1) Understand it advises rewriting history and force-pushing to remove attributions—do NOT run those commands on shared or protected branches without team coordination; prefer non-destructive fixes first. (2) Installing the commit-msg hook will block commits containing forbidden text locally—test the hook in a sandbox repo and ensure everyone on the team agrees to the policy. (3) Consider legal/ethical/licensing implications of removing attribution in your organization (some projects or contributors may require explicit attribution). If you accept those operational and governance tradeoffs, the skill itself contains no unexpected network calls, credentials, or installers.

Git & PR Workflow Standards

Core Principles

• Small PRs: ≤300 LOC changed ideally
• Commit often: Early, meaningful commits with clear messages
• Linear history: Prefer rebase over merge commits
• Professional: No AI attribution, no tool branding, clean descriptions

🚨 ABSOLUTE ZERO-TOLERANCE RULE: NO AI ATTRIBUTION 🚨

NEVER, UNDER ANY CIRCUMSTANCES, include ANY of the following in:

• Git commit messages
• Pull request descriptions
• Issue comments
• GitHub discussions
• Code comments
• Documentation
• ANY public-facing repository content

❌ STRICTLY FORBIDDEN TEXT - NEVER USE

• "Claude"
• "Anthropic"
• "claude.com"
• "Claude Code"
• "Claude Desktop"
• "Generated with Claude"
• "Co-Authored-By: Claude"
• "🤖 Generated with Claude Code"
• "Co-Authored-By: Claude [e-mail]"
• Any emoji followed by "Generated with" or "Powered by"
• Any reference to AI assistants, AI code generation, or automated tools
• Any branding, attribution, or links to third-party AI services

✅ CORRECT FORMAT - ALWAYS USE

• Clean, professional commit messages
• Clear description of what changed
• Explanation of why the change was made
• No attribution, no branding, no tool references

Examples

❌ FORBIDDEN COMMIT

Add multi-dimension vector support

- Support for 384, 768, 1024, and 1536 dimensions
- Update validation logic for new dimensions
- Add comprehensive test coverage

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[e-mail]>

✅ CORRECT COMMIT

Add multi-dimension vector support

- Support for 384, 768, 1024, and 1536 dimensions
- Update validation logic for new dimensions
- Add comprehensive test coverage

❌ FORBIDDEN PR DESCRIPTION

## Summary
Implemented new authentication flow with JWT tokens.

## Test Plan
All tests passing.

---
🤖 Powered by Claude

✅ CORRECT PR DESCRIPTION

## Summary
Implemented new authentication flow with JWT tokens.

## Test Plan
All tests passing.

Enforcement

• ZERO TOLERANCE rule with NO EXCEPTIONS
• Every commit must be verified before pushing
• Every PR must be reviewed for attribution before creating
• If attribution is found, it must be removed immediately via force push or amendment
• This rule applies to ALL repositories, ALL projects, ALL commits
• Violations compromise the professional appearance of our work

Why This Matters

• Maintains professional repository appearance
• Avoids unwanted third-party attribution
• Ensures our work is presented as our own
• Prevents confusion about authorship and ownership
• Compliance with company branding guidelines

PR Requirements

Every PR must include:

• Problem/Context: What issue are we solving and why?
• Solution summary: How does this change address the problem?
• Test plan: Commands + results proving functionality
• Risk/rollback: Potential issues and how to revert if needed
• Story link + Type + Estimate: Link to issue/story with type (feature/bug/chore) and points

Reference Files

See references/ai-attribution-enforcement.md for comprehensive forbidden text list and enforcement details.

See references/pr-templates.md for complete PR templates for feature, bug, and chore PRs.

See references/branch-conventions.md for branch naming patterns and examples.