本文へ移動
cccskills
無料GitHub で公開

ln-162-skill-reviewer

Universal skill reviewer: SKILL mode (D1-D9 + M1-M5) or COMMAND mode (skill review)

インストール方法を見る

含まれるファイル(6)

  • SKILL.md7.7 KB
  • references/automated_checks_skill_mode.md4.7 KB
  • references/command_review_criteria.md2.1 KB
  • references/dimensions_d1_d9.md5.3 KB
  • references/intent_m1_m5.md3.4 KB
  • references/run_checks.sh7.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.

ln-162-skill-reviewer

Type: L3 Worker (standalone-capable) Category: 1XX Documentation Pipeline Coordinator: ln-160-docs-skill-extractor (optional)

Universal skill reviewer with two auto-detected modes. Invocable standalone or by ln-160 coordinator.


Mode Detection

ConditionModeReview Profile
ln-*/SKILL.md files exist in CWDSKILLFull D1-D9 + M1-M5
.pi/skills/*.md files existCOMMANDStructural + actionability
Both existSKILL (default)Override: $ARGUMENTS = commands

Input

$ARGUMENTS options:

  • Empty -> auto-detect mode + auto-detect scope
  • ln-400 ln-500 -> SKILL mode, specific skills
  • commands -> COMMAND mode, all SKILL.md files
  • deploy.md run-tests.md -> COMMAND mode, specific files

When invoked by ln-160 coordinator: receives list of file paths to review in COMMAND mode.


SKILL Mode

Review SKILL.md files against 9 structural dimensions + 5 intent checks. Fix in-place. Report with PASS/FAIL verdict.

Phase 1: Scope Detection

If $ARGUMENTS provided: treat each token as a skill directory prefix (e.g., ln-400 matches ln-400-story-executor/). Glob {prefix}*/SKILL.md per token.

If $ARGUMENTS empty: auto-detect from git:

git diff --name-only HEAD
git diff --name-only --cached
git ls-files --others --exclude-standard

Extract unique skill dirs (pattern ln-\d+-[^/]+) and shared paths (shared/). If shared files changed, Grep all ln-*/SKILL.md for references to changed filenames.

Build scope:

  1. Primary -- skills with directly changed files
  2. Affected -- skills referencing changed shared files
  3. Dependencies -- for each primary skill, extract ln-\d{3,4} references from its SKILL.md (callers, callees, worker tables)

Deduplicate. Report: Scope: N primary, M affected, K dependency skills.

Phase 2: Automated Verification

Run the automated checks script against all SKILL.md files in scope:

bash references/run_checks.sh {scoped SKILL.md files}

Record failures -- they feed D7/D8 as pre-verified violations. Every FAIL is confirmed -- no judgment needed, no skipping. Check definitions: references/automated_checks_skill_mode.md.

Phase 3: Nine-Dimension Review

MANDATORY READ: Load references/dimensions_d1_d9.md and docs/architecture/SKILL_ARCHITECTURE_GUIDE.md

Read every SKILL.md in scope. Check ALL dimensions across ALL skills. Phase 2 failures are pre-verified -- include directly, do not re-check.

Phase 4: Intent Review

MANDATORY READ: Load references/intent_m1_m5.md

Evaluate DESIGN INTENT of changes. Applies to primary skills only. For each primary skill, read the git diff (git diff HEAD -- {skill_dir}/).

Phase 5: Fix

For each finding:

  • Fixable (wrong path, stale ref, missing bidirectional ref, duplicated content) -- fix immediately via Edit
  • Ambiguous (conflicting thresholds where correct value unclear) -- list in report, do NOT guess
  • SIMPLIFY (from Phase 4) with unambiguous action -- fix immediately
  • REVERT (from Phase 4) -- roll back the change via Edit
  • RETHINK (from Phase 4) -- do NOT fix, pass to Phase 6 report

Phase 6: Report

Verdict rules:

  • Any D1-D9 violation NOT auto-fixed -> FAIL
  • Only RETHINK findings (no unfixed violations) -> PASS with CONCERNS
  • Zero findings -> PASS
## Skill Coherence Review -- {PASS|PASS with CONCERNS|FAIL}

**Scope:** {list of reviewed skills}
**Verdict:** {verdict}

### Automated Checks (Phase 2)
| Check | Result | Failures |
|-------|--------|----------|
| Frontmatter (D7) | {PASS/FAIL} | {list or --} |
| Version/Date (D7) | {PASS/FAIL} | {list or --} |
| Size <=800 (D8) | {PASS/FAIL} | {list or --} |
| Description <=200 (D8) | {PASS/FAIL} | {list or --} |
| MANDATORY READ paths (D2) | {PASS/FAIL} | {list or --} |
| Orphan references (D7) | {PASS/FAIL} | {list or --} |
| Passive file refs (D2) | {PASS/FAIL} | {list or --} |
| Definition of Done (D7) | {PASS/FAIL} | {list or --} |
| Meta-Analysis L1/L2 (D7) | {PASS/FAIL} | {list or --} |
| Marketplace paths (D8, optional) | {PASS/FAIL/SKIP} | {list or --} |
| Root docs stale names (D6) | {PASS/FAIL} | {list or --} |
| Skill count accuracy (D8) | {PASS/FAIL} | {list or --} |

### Fixed ({count})
| # | Skill | Dim | Issue | Fix Applied |
|---|-------|-----|-------|-------------|

### Intent Findings ({count})
**M5 Classification:** {R} requested, {D} derived, {S} speculative ({K} kept, {V} reverted)

| # | Skill | Dim | Finding | Category |
|---|-------|-----|---------|----------|

### Remaining Concerns ({count})
| # | Skill | Dim | Issue | Why Not Auto-Fixed |
|---|-------|-----|-------|--------------------|

### Clean
Dimensions with no findings: {list}

If zero findings: All 9 structural dimensions + 5 intent checks clean. PASS.

Phase 7: Volatile Numbers Cleanup

Skill/plugin/category counts go stale after every add/remove. One rule: counts ONLY in README.md badge (skills-NNN). Everywhere else -- no hardcoded counts.

Remove from any file (including marketplace.json descriptions, PROJECT.md, AGENTS.md, CHANGELOG.md, SKILL.md):

  • Total skill counts, per-plugin counts, per-category counts
  • Worker/coordinator counts referencing OTHER skills (a skill's OWN internals are fine)

Phase 2 automated check verifies README badge matches actual skill count on disk -- fix if FAIL.


COMMAND Mode

Review .pi/skills/*.md files against structural + actionability criteria.

MANDATORY READ: Load references/command_review_criteria.md

Phase 1: Scope Detection

If file paths provided: review those files. If commands keyword: Glob SKILL.md files. If invoked by ln-160: use file list from coordinator.

Phase 2: Review

For each command file, apply all criteria from references/command_review_criteria.md.

Phase 3: Fix

Auto-fix where possible (add missing frontmatter, truncate description). Flag unfixable issues.

Phase 4: Report

## Command Review -- {N} files

| File | Verdict | Issues |
|------|---------|--------|

Verdicts: PASS / FIXED / WARN
Pass rate: {X}%

Rules

  • Automated checks (Phase 2) are NON-NEGOTIABLE -- every FAIL must appear in report
  • Do NOT skip any dimension for any skill in scope
  • If unsure whether something violates a rule -- it violates the rule (strict interpretation)
  • Read ALL skills in scope before reporting
  • Fix errors immediately, do not defer
  • Do NOT update versions or dates unless user explicitly requests it
  • shared/ changes affect every skill that references them -- check reverse dependencies
  • Intent review (M1-M5) evaluates DESIGN, not correctness -- findings are judgment-based
  • RETHINK findings are advisory -- explain WHY, author decides WHETHER to act
  • REVERT findings are executed immediately -- changes without concrete defect are rolled back
  • SPECULATIVE items (M5) without user response default to REVERT -- no silent acceptance of model-generated additions

Definition of Done

  • Scope detected (primary + affected + dependency skills)
  • Phase 2 automated checks executed for all skills in scope
  • D1-D9 dimensions reviewed across all skills
  • M1-M5 intent evaluated for primary skills
  • Fixable findings auto-fixed via Edit
  • Report generated with PASS/PASS with CONCERNS/FAIL verdict

Version: 1.0.0 Last Updated: 2026-03-13

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.

日本語の概要は準備中です。原文の説明を表示しています。

tensology/decisionsai172026年10月13日 更新

tensology のスキルをすべて見る

このスキルの問題を報告する