agentleFS
Sign inStart free
arslanvuzmalarslanvuzmal/VoxCircuit/.agents/skills/github-authorship-audit/SKILL.md

github-authorship-audit

Skill2 starsChanged 3 months agoMITView on GitHub

Scans Git history, commit trailers, author identity, and codebase text to ensure ZERO automated AI or bot credits exist.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use before every Git commit, before pushing to GitHub (arslanvuzmal/voxdesk-ai), and prior to final project completion.

    line 10
  2. Distinctive:

    Search for forbidden attribution strings across entire codebase: "Co-Authored-By:", "Generated-By:", "Built with Antigravity", "Created by …

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitHub Authorship Audit Skill

When to Use

Use before every Git commit, before pushing to GitHub (arslanvuzmal/voxdesk-ai), and prior to final project completion.

Inputs Required

  • Local Git log and configuration.
  • Project repository root files.

Step-by-Step Process

  1. Inspect git identity: git config --get user.name -> MUST BE Arslan Vuzmal Lone git config --get user.email -> MUST BE arslanvuzmallone@gmail.com
  2. Scan commit log history: git log --format="%h | AUTHOR=%an <%ae> | COMMITTER=%cn <%ce> | %s" -30
  3. Search for forbidden attribution strings across entire codebase: "Co-Authored-By:", "Generated-By:", "Built with Antigravity", "Created by Gemini", "Claude", "Anthropic", "AI-generated repository", "Antigravity-Session:".
  4. Confirm docs/AUTHORSHIP_AUDIT.md status displays: AUTOMATED ASSISTANT CONTRIBUTOR STATUS: NOT PRESENT — VERIFIED

Decision Tree

  • Is any forbidden attribution string or improper author found?
    • YES -> BLOCK COMMIT/PUSH -> Fix git config / scrub commit log -> Re-audit.
    • NO -> Pass authorship audit.

Validation Checklist

  • Sole Author & Committer: Arslan Vuzmal Lone arslanvuzmallone@gmail.com.
  • 0 AI co-author trailers in any commit message.
  • README and package manifests credit Arslan Vuzmal Lone exclusively.

Failure Conditions

  • Presence of any AI assistant credit or mismatched git author identity.

Expected Output

Verified AUTHORSHIP_AUDIT.md confirming 100% clean human authorship status.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free