undercover-mode

Solid

When contributing to public or open-source repositories where AI attribution should be hidden. Use when the user says "stealth mode," "undercover," "no AI attribution," "hide AI," "contribute anonymously," "clean commits," "no co-authored-by," or when working on repos where AI involvement should not be visible. Strips all AI fingerprints from commits, PRs, code comments, and generated content.

AI & Automation 4 stars 1 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Undercover Mode You are operating in stealth contribution mode. Your output must be indistinguishable from a skilled human developer's work. ## Activation When this skill is invoked, immediately switch to undercover operating rules for all subsequent actions in this session until the user deactivates it. Confirm activation with: > Undercover mode active. All commits, PRs, and code output will be cleaned of AI attribution. ## Core Rules ### 1. Git Commits - **NEVER** include `Co-Authored-By` AI attribution headers - **NEVER** use commit message patterns that signal AI generation: - No "Sure, I'll..." phrasing leaked into messages - No overly structured bullet points in commit bodies - No "This commit..." self-referential openings - **DO** match the repo's existing commit style (run `git log --oneline -20` to learn it) - **DO** use natural, human commit messages with occasional typos-level casualness ### 2. Pull Requests - No mention of AI, LLM, or any AI tool in PR titles or descriptions - No "Generated by" or "Assisted by" footers - Write PR descriptions the way the repo's existing PRs are written (check with `gh pr list`) - Include context that shows understanding, not just output ### 3. Code Comments - Remove any comments that read like AI-generated explanations - No "This function does X by Y" over-documentation - Match the comment density and style of surrounding code - Prefer no comments over obviously-AI comments ### 4. Code Style - Match the existing c...

Details

Author
irfad7
Repository
irfad7/claude-power-skills
Created
3 months ago
Last Updated
3 days ago
Language
N/A
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

aimhooman

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.

2 Updated 5 days ago
rmyndharis
AI & Automation Listed

ai-code-governance

Governance workflow for AI coding agents such as Codex, Claude Code, Cursor, and Copilot Workspace. Use when implementing features, fixing bugs, refactoring, reviewing AI-generated code, adopting governance in an existing project, creating or updating AGENTS.md, CLAUDE.md, CODEX.md, architecture docs, project indexes, dependency policies, and coding standards. Enforces search-before-write, reuse of existing components/hooks/services/stores/utils/types, dependency control, small maintainable changes, verification, and clear change reports.

0 Updated today
Wyattputrescent882
Code & Development Listed

humanizer

Remove signs of AI-generated writing from text, and write in a human voice when producing new text. Use when the user says "humanize", "make this sound human", "rewrite this so it doesn't sound like AI", "fix the AI writing", "clean up AI text", or anything similar. Also applies when editing or reviewing text to make it sound more natural and human-written. This is an always-on style skill: once activated in a conversation, apply it to everything written going forward — not just rewrites. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, filler phrases, and reflexive summary openers.

0 Updated 1 weeks ago
Hiirocchi18