Audit GitHub repositories and git history for AI-attribution traces.
npx skills add https://github.com/yusuftuhh/vibecheck --skill vibecheck-yusuftuhh
Please help me install this Agent Skill. Skill: vibecheck Source: https://github.com/yusuftuhh/vibecheck/tree/main/skill Command: npx skills add https://github.com/yusuftuhh/vibecheck --skill vibecheck-yusuftuhh
It helps you detect and eliminate AI-attribution signals (like Co-Authored-By footers and AI-typical phrasing) that can appear across your GitHub activity before they affect how others perceive your work.
Use cases include pre-publish checks for an open-source project, profile audits for recruiter-facing signals, and targeted cleanup of leftover AI helper files or wording in READMEs/bios/comments.
Run the audit by asking: scan my GitHub repo, profile, and any provided gists or PRs for AI-attribution traces and list the findings grouped by severity.
High-intent search queries and answers about installing and using this skill.
To scan for AI authorship traces, the audit reviews GitHub repositories, profiles, gists, and issue/PR comments for Co-Authored-By bot footers and AI-typical phrasing. It produces JSON findings with IDs and severity rankings for user review.
Yes, you can remove Co-Authored-By footers from local git history by running a local audit to find commit-level indicators. The scan-and-fix CLI flow presents actionable items and applies edits, including force-push scenarios, only after explicit user approval.
The best way to clean up AI-typical phrasing in issue and PR comments is scanning your GitHub presence to detect AI-coding signals. Findings are grouped by severity as selectable items, allowing targeted cleanup of wording before recruiters review your profile.
No, the AI cleanup process does not automatically rewrite commit metadata. It identifies bot footers and authorship signals but applies fixes via a guided flow that requires explicit user confirmation before editing any Git hosting workflows or local history.
You need to audit your GitHub presence for AI attribution signals during pre-publish reputation checks for open-source projects and profile hygiene for recruiter-facing reviews. This detects Co-Authored-By footers and leftover AI helper artifacts before others evaluate your work.
A key limitation when rewriting commit history to remove AI authorship traces is that applying changes to local git history may require force-push scenarios. The audit generates JSON findings but restricts modifications to only user-approved fixes to prevent unintended repository alterations.
BermudaLocalsConfigure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.
kid-sidEnforce conventional commits, branch naming, and safe force-push rules in Git workflows.
ratacatConvert documentation sites into a single Markdown file for AI context.
simonheimlicherGenerate Conventional Commits messages with selective file staging commands.
