research-lint
Run the research corpus lint ruleset to detect structural and referential integrity issues — orphan notes, missing frontmatter, broken references, missing GRADE assessments.
What this skill does
# Research Lint Run the research corpus lint ruleset against `.aiwg/research/` to detect structural and referential integrity issues. ## Triggers - "lint the research corpus" - "check research integrity" - "validate research notes" - "sweep the corpus for issues" - "research lint" - `/research-lint` ## Parameters ### `[target]` (optional) Path to lint. Defaults to `.aiwg/research/`. ### `--fix` (optional) Attempt auto-fixes for fixable issues (add missing frontmatter defaults, correct formatting). ### `--format` (optional) Output format: `full` (default), `summary`, or `json`. ### `--ci` (optional) CI mode — exit code reflects pass/fail. ### `--fail-on` (optional) Severity threshold for failure: `error` (default), `warn`, or `info`. ## Execution Flow ### Phase 1: Run Lint Execute the lint runner against the research corpus: ```bash aiwg lint .aiwg/research/ --ruleset research --format full ``` This checks all 11 rules in the research ruleset: | Rule | Severity | What it checks | |------|----------|---------------| | `ref-frontmatter` | error | Required frontmatter fields present | | `ref-id-unique` | error | No duplicate REF-XXX identifiers | | `ref-id-format` | warn | REF identifiers follow `REF-NNN` naming | | `citation-resolves` | error | REF-XXX references point to existing notes | | `grade-present` | warn | GRADE quality assessment in frontmatter | | `provenance-present` | warn | Provenance metadata present | | `cross-ref-bidirectional` | info | Related refs linked both ways | | `orphan-detection` | info | Notes with no inbound references | | `frontmatter-date-format` | warn | Dates follow ISO 8601 | | `source-file-exists` | error | Referenced source files exist | ### Phase 2: Report Results Display the results grouped by file with severity indicators: - Errors: must be fixed for corpus integrity - Warnings: should be addressed for corpus quality - Info: suggestions for improvement ### Phase 3: Auto-Fix (if --fix) When `--fix` is specified, attempt automatic corrections: 1. **Missing frontmatter fields** — Add fields with sensible defaults: - `status: pending` - `documented_date: <today>` - `tags: []` 2. **Date format** — Convert dates to ISO 8601 3. **Missing GRADE** — Add `grade_rating: null` placeholder Write corrections in place and re-run lint to verify fixes. ## Integration Points | Component | Relationship | |-----------|-------------| | `aiwg lint` | Underlying CLI command this skill wraps | | `corpus-health` | Lint results feed into health scoring | | `induct-research` | Post-induction hook can trigger lint on new notes | | `ralph` loops | Lint pass as completion gate | | CI/CD | `aiwg lint --ci --ruleset research --fail-on error` | ## Examples ```bash # Full corpus lint /research-lint # Quick summary /research-lint --format summary # CI mode (exit code) /research-lint --ci --fail-on warn # Lint specific directory /research-lint .aiwg/research/findings/ # Auto-fix what's fixable /research-lint --fix # JSON output for programmatic use /research-lint --format json ``` ## Sidecar-level integrity (use `sidecar-lint`) This skill runs the note/corpus-wide ruleset. It does **not** inspect citation **sidecar** internals (Outgoing/Incoming sections, edge tables, doubled-append duplicate headers, `(see REF doc)` authors, `affiliation-primary` canonicalization, zero-edge sidecar orphans). For those, use the companion `sidecar-lint` skill (`aiwg corpus sidecar-lint` / `sidecar-repair`). The two compose — `research-lint` for note-level referential integrity, `sidecar-lint` for citation-sidecar structure — neither duplicates the other. ## References - @$AIWG_ROOT/agentic/code/frameworks/research-complete/lint/ruleset.yaml - @$AIWG_ROOT/src/lint/cli.ts - @$AIWG_ROOT/src/lint/runner.ts - @$AIWG_ROOT/agentic/code/frameworks/research-complete/skills/sidecar-lint/SKILL.md — sidecar-structural lint + repair
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.