Auditing Repositories

Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst

5 starsTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add tomada1114/tomada-claude-plugins

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add tomada1114/tomada-claude-plugins --skill auditing-repositories
Manual install
git clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/auditing-repositories ~/.claude/skills/auditing-repositories

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Auditing repositories

Without this skill, a review of a whole repository reads a few files, lists generic
smells, and either files nothing or files noise. This skill does three things instead.
It measures the repository against the design the repository itself declares. It
spends cheap context on collecting evidence and expensive judgment on the root cause
and the target design. And it turns each evidenced finding into an issue that an
implementing agent can ship test-first without asking back. "The current design is
right" is a valid outcome; the report records what was examined and kept.

## Contract

**Input:** free-form, run from inside the target repository. Optional narrowing:

- lens names: `architecture`, `tests`, `code-quality`, `tooling` (default: all four)
- paths, which limit the survey
- `full`, which forces a whole-repository audit when an incremental one would apply
- `dry-run` (also "report only", "don't file"), which stops after drafting

**Authorization:** invoking this skill authorizes creating issues, labels and native
issue links in the audited repository, and in its template repository for inherited
findings. It authorizes nothing else. In particular, it makes no code changes, no
commits, and no comments on or closing of existing issues.

**Output:** `$RUN = ${AGENT_SKILL_STATE_DIR:-$HOME/.local/state/agent-skills}/auditing-repositories/<owner>-<repo>/runs/<YYYY-MM-DD>/`,
Read the full skill on GitHub

Details

Skill name
auditing-repositories
Path
tomada-kit/skills/auditing-repositories/SKILL.md
Repo updated
12 November 2026

FAQ

What does the Auditing Repositories skill do?

Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst

How do I install the Auditing Repositories skill?

Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Auditing Repositories popular?

It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.

Related skills

Auditing Prompt Docs

5

tomada1114/tomada-claude-plugins

Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m

AI, LLMs & Agents

Authoring Goal Prompts

5

tomada1114/tomada-claude-plugins

Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de

AI, LLMs & Agents

Bootstrapping From Templates

5

tomada1114/tomada-claude-plugins

Cut a new GitHub repository from one of the user's template repositories and bring it to a clean first commit: create it from the template (public by default) with scripts/create_from_template.py, clone it under ghq, follow the template's own starting-an-app procedure for the rename or bootstrap (a script, a just recipe, or a placeholder inventory), write AGENTS.md's Product section from signed-off requirements, copy kickoff drafts into docs/, run the template's checks, sync its labels, and push. Use when creating a repository from a template, running a template's bootstrap or rename, a placeh

Writing & Content

Bun Dates and Times

9

jarle/bun-skills

Learn how to manipulate time and dates in your Bun tests using setSystemTime and Jest compatibility functions

Testing & QA

Bio Read Alignment Bowtie2 Alignment

9

hackernoon/cuttlefish-agent-skills

Aligns DNA short reads to a reference with Bowtie2, choosing end-to-end (whole read must align) vs local (soft-clip read ends) mode and a sensitivity preset; the de-facto aligner for ChIP-seq, ATAC-seq, and CUT&RUN, where fragment-geometry flags (--no-mixed, --no-discordant, --dovetail, -X) and a tool-appropriate MAPQ filter feed the peak caller. Use when aligning ChIP/ATAC/CUT&RUN reads, when read ends are adapter-contaminated and need soft-clipping, or when a tunable sensitivity/speed preset is wanted. DNA variant calling prefers bwa-alignment; RNA spliced alignment is star-alignment/hisat2-

Testing & QA

Bun DOM Testing

9

jarle/bun-skills

Learn how to test DOM elements and components using Bun with happy-dom and React Testing Library

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.