aimhoomanlisted

Keep AI tooling artifacts out of Git. Use whenever staging, committing, or pushing changes: block AI session/state files (.claude/session.json, .codex/history, .copilot, .cursor/session, .aider.*, .specstory, .agent) and unwanted AI attribution in commit messages (Co-authored-by an AI, "Generated with AI"). Also use when the user says "aimhooman", "ship it like a hooman", or asks to clean AI residue before a commit.
rmyndharis/aimhooman · ★ 4 · AI & Automation · score 75

Install: claude install-skill rmyndharis/aimhooman

# aimhooman  This repository uses aimhooman to keep AI tooling artifacts out of Git history. Its policy: - Never stage or commit local AI session/state files. Examples include `.claude.json`, `.claude/session*.json`, `.claude/history*`, `.claude/todos/*`, `.claude/shell-snapshots/*`, `.claude/statsig/*`, `.claude/projects/*`, `.claude/logs/*`, `.codex/sessions/*`, `.codex/history*`, `.codex/log/*`, `.codex/logs/*`, `.copilot/*`, `.cursor/session*`, `.cursor/chats/*`, `.cursor/logs/*`, `.aider.*`, `.specstory/*`, `.continue/sessions/*`, `.playwright-mcp/*`, `.remember/*`, `.superpowers/*`, and `.agent/*`. The examples are not exhaustive; the packaged `rules/paths.json` is the detection source of truth for these artifacts. If one is staged, unstage it and keep it out of Git instead. - Never commit secrets: a real `.env` (not `.env.example`), private keys (`id_rsa` and files containing a private-key header), `.aws/credentials`, `.claude/.credentials.json`, service-account keys, or a provider API key (GitHub, GitLab, npm, Slack, Anthropic, OpenAI, Google, Stripe, Hugging Face, SendGrid). Public certificates are allowed. aimhooman does not scan for secrets — this rule is on you, and a dedicated scanner such as gitleaks is the right backstop for it. - Never add AI attribution to commit messages: no `Co-authored-by` trailer naming an AI (Claude, Copilot, Codex), no "Generated with/by <AI>" lines, no AI-service nor