From research-convensions
Audits a repository for beginner-level best-practice violations covering README, tests, CI, Git history, issues, PRs, branch discipline, docs, coding style, security, and maintainability. Produces a scorecard with evidence and prioritized fixes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/research-convensions:repo-hygiene-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Audit a repository as a beginner-friendly scorecard. Ground every judgment in visible evidence, and give concrete next steps instead of vague advice.
Audit a repository as a beginner-friendly scorecard. Ground every judgment in visible evidence, and give concrete next steps instead of vague advice.
Use these references as needed:
references/scorecard-rubric.md: default checks and severity rules.references/git-history-audit.md: commit, branch, issue, and PR checks.Prefer read-only commands:
pwd
find . -maxdepth 3 -type f | sort | head -200
git status --short
git branch -a -vv
git log --oneline --decorate --all -n 120
git remote -v
find .github -maxdepth 3 -type f | sort
If GitHub CLI is configured, optionally enrich the local evidence:
gh pr list --state all --limit 30 --json number,title,state,headRefName,baseRefName,mergedAt,closedAt,author
gh issue list --state all --limit 30 --json number,title,state,labels,createdAt,closedAt,author
Do not rewrite history, delete branches, push, create issues, or edit files unless the user explicitly asks for remediation.
Start with a compact summary:
Overall: Warn
Best signals: ...
Highest-risk gaps: ...
Recommended first fixes: ...
Then provide a scorecard:
| Area | Status | Evidence | Why it matters | Next step |
|---|---|---|---|---|
| README | Pass | README.md has setup and examples | New users can start | Keep current |
Use statuses exactly:
Pass: visible evidence meets beginner expectations.Warn: usable, but confusing, incomplete, stale, or inconsistent.Fail: missing or likely to block contributors.Not visible: cannot be assessed from local evidence.End with a short prioritized fix list. Keep it practical and ordered by value.
Do not over-penalize small or early repos. A beginner repo can still pass if it has clear setup, tests, and review flow.
Use Fail for gaps that block basic collaboration:
Use Warn for teachable inconsistencies:
update.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub codingthrust/templates --plugin research-convensions