Ainative Git Workflow
v1.0.0Git commit, PR, and branching standards with ZERO TOLERANCE for AI attribution. Use when (1) Creating commits, (2) Writing commit messages, (3) Creating pull...
⭐ 0· 85·0 current·0 all-time
byToby Morning@urbantech
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & 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.Like a lobster shell, security has layers — review code before you run it.
latestvk970me3m18fkcpbmpqh9088nyx83na06
License
MIT-0
Free to use, modify, and redistribute. No attribution required.