# Subject Audit

Review AnimeGarden animation resource-to-Bangumi Subject bindings for a specified time...

- Repository: https://github.com/yjl9903/AnimeGarden (1390 stars)
- Category: Design
- License: AGPL-3.0
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add yjl9903/AnimeGarden --skill subject-audit -g -a claude-code -y`
Codex: `npx skills add yjl9903/AnimeGarden --skill subject-audit -g -a codex -y`
Cursor: `npx skills add yjl9903/AnimeGarden --skill subject-audit -g -a cursor -y`
Gemini CLI: `npx skills add yjl9903/AnimeGarden --skill subject-audit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add yjl9903/AnimeGarden`

## Description

Review AnimeGarden animation resource-to-Bangumi Subject bindings for a specified time range, identify missing or incorrect bindings, and report evidence-backed Subject search improvements. Use for manager-side audits; online binding corrections are optional and require explicit user confirmation.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# AnimeGarden Subject Audit

Review every animation resource in a requested time range, determine which registered Bangumi
Subject it most likely belongs to, and assess both its current binding and the target Subject's search
coverage. The current `subjectId` and search configuration are evidence about system state rather
than the basis for attribution.

The standard path produces a read-only audit report. An optional confirmed step can apply reliable
target Subject IDs to current online resources before the report is finalized.

Read [references/audit-rules.md](references/audit-rules.md) for the attribution standard, search
diagnosis, and report format.

## Workflow

### 1. Collect the audit evidence

Create a fresh task-scoped temporary directory and run from this skill directory:

```bash
node scripts/fetch-resources.mjs --start <ISO timestamp> --end <ISO timestamp> --output <tmp-dir>/resources.jsonl
node scripts/fetch-subjects.mjs --output <tmp-dir>/subjects.jsonl
```

The first file contains all animation resources in the interval and their current `subjectId`; the
second contains the complete registered Subject index. Confirm the declared counts, then review the
resource file in manageable batches until every record has been assessed.

### 2. Attribute every resource

Identify the work, installment, and episode from the complete release context. For an existing
binding, evaluate the bound Subject alongside other plausible registered Subjects. For an unbound
resource, search the registry using the title forms suggested by the release.

Weigh the evidence that is informative for that resource: names and aliases, season or part context,
episode progression, publication timing, related Subjects, and neighboring releases. Their relevance
varies by title family, so attribution follows the explanation that best fits the whole release
context. Record uncertainty when the evidence does not support one clear Subject.

The rest: https://github.com/yjl9903/AnimeGarden/blob/HEAD/.agents/skills/subject-audit/SKILL.md