sidecar-lint
Lint and repair citation sidecars in a research corpus — structural integrity (missing Outgoing/Incoming sections, missing frontmatter ref/title/type, doubled-append duplicate table headers), zero-edge orphan detection, (see REF doc) author backfill from the analysis citation block, and affiliation-primary canonicalization to PROF-O slugs. Runs via `aiwg corpus sidecar-lint` / `aiwg corpus sidecar-repair`.
What this skill does
# Sidecar Lint & Repair
Citation-sidecar hygiene for a research corpus. Two read-only diagnostics
(`sidecar-lint`, `sidecar-lint --orphans`) and two repair tools
(`sidecar-repair`) that backfill authors and canonicalize affiliations.
These operate on `documentation/citations/REF-*-citations.md` under the
resolved corpus root (`AIWG_CORPUS_ROOT` env > `research.corpusRoot` in
`.aiwg/aiwg.config` > cwd).
## How to run
```bash
# Structural lint — missing sections/frontmatter, duplicate table headers
aiwg corpus sidecar-lint
# Zero-edge orphans (no incoming AND no outgoing edges), titled from the analysis doc
aiwg corpus sidecar-lint --orphans
# Repair: backfill (see REF doc) authors + normalize affiliations — DRY-RUN
aiwg corpus sidecar-repair
# Repair for real
aiwg corpus sidecar-repair --write
# Restrict to one repair
aiwg corpus sidecar-repair --authors-only --write
aiwg corpus sidecar-repair --affiliations-only --write
# Write a report to a file (resolved against the corpus root)
aiwg corpus sidecar-lint --out reports/sidecar-lint.txt
```
## What `sidecar-lint` checks
| Issue | Meaning |
|-------|---------|
| `missing-frontmatter` / `malformed-frontmatter` | No `---` block, or no closing `---` |
| `frontmatter-missing-{ref,title,type}` | Required sidecar frontmatter field absent |
| `missing-outgoing-section` / `missing-incoming-section` | No Outgoing/Incoming H2 (merge-redirects with `status: merged` / `MERGED INTO` are exempt) |
| `duplicate-table-headers-count=N` | Two `\| # \| Title` headers under one sub-header — the doubled-append signature |
`--orphans` lists sidecars with **zero** REF edges in either section (lenient
scan: any `REF-NNN` token in an Outgoing/Incoming section counts as an edge,
regardless of table-column naming).
## What `sidecar-repair` does
- **Authors** — for sidecars whose `authors:` still contains `(see REF doc)`,
parse the analysis doc's `## Citation` block and write structured
`authors: - name:` entries. Handles `Last, F. M.` initials, `&`/`and`
separators, `et al.` truncation, and institutional single-authors.
- **Affiliations** — normalize `affiliation-primary` to a canonical
`PROF-O-{slug}` when unambiguous; multi-org / parenthetical / unknown values
are left untouched and reported as ambiguous. The canonical map ships as a
default and is **overridable per-corpus** via
`documentation/profiles/orgs/affiliation-map.yaml` (slug → variant names).
Both default to **dry-run**; nothing is written without `--write`.
## Reconciliation with `research-lint`
This is the **sidecar-structural** layer. The `research-lint` skill runs the
generic `aiwg lint --ruleset research` over `.aiwg/research/` (note-level
frontmatter, REF-id uniqueness, citation-resolves, note orphans). Those checks
do not look inside citation-sidecar structure. Use:
- **`research-lint`** for note/corpus-wide referential integrity and the lint ruleset engine.
- **`sidecar-lint`** for the citation-sidecar internals (Outgoing/Incoming sections, edge tables, author/affiliation metadata) and edge-graph orphans.
They compose; neither duplicates the other.
## Triggers
- "lint the citation sidecars"
- "find orphaned sidecars"
- "fix (see REF doc) authors"
- "normalize affiliations to PROF-O"
- "sidecar lint" / "sidecar repair"
## Notes
- All four operations are TS-native (`src/artifacts/corpus-tools/sidecar-lint.ts`,
`sidecar-repair.ts`) — ports of section9 `lint_sidecars.py`, `find_orphans.py`,
`fix_broken_authors.py`, `normalize_affiliation.py`.
- Author backfill matches the source's trailing-dot handling (a final initial
like `Hinton, G.` is stored `Hinton, G`) for idempotency against corpora
already processed by the original script.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.