h-semio-review

Solid

INTERNAL SUBROUTINE — semiotic / fanout audit on a concept rename, deprecation sweep, or doc-vs-code consistency check. Walks all carriers (filenames, manifests, stale refs, review surfaces, dashboards, prompts) until fixed-point clean, because one-shot text replacement creates rework when carriers diverge. Manual invocation only. Do not auto-select for general work — for code review use Claude Code review; for FPF reasoning about decisions use h-frame / h-decide.

Code & Development 1,338 stars 104 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 89/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# h-semio-review — Fanout audit (subroutine) You are running the semiotic fanout audit per FPF X-FANOUT-AUDIT and the semiotics_slideument discipline. The premise: on concept rename / deprecation / spec consistency check, the change must sweep ALL carriers — prose, filenames, manifests, review bundles, provenance, tests, schemas — until fixed-point clean. Skipping carriers leaves zombie references that mislead future operators and agents. Explicit-only — `disable-model-invocation: true`. ## Step 1 — Identify the object of talk What CONCEPT or TERM is being renamed / deprecated / audited? Get it from the operator explicitly. Bad: "audit the docs"; good: "rename `Service` to `EnablingSystem` across docs and code". If renaming, capture both old and new names. If deprecating, capture the old name and the replacement (or explicit "no replacement"). ## Step 2 — Map carriers exhaustively Run discovery across all carrier surfaces: ```bash # Prose carriers grep -rl "<term>" --include="*.md" --include="*.txt" --include="*.rst" # Code carriers grep -rl "<term>" --include="*.go" --include="*.py" --include="*.ts" --include="*.tsx" --include="*.rs" \ --include="*.java" --include="*.js" --include="*.jsx" # Manifest carriers grep -rl "<term>" --include="package.json" --include="Cargo.toml" --include="pyproject.toml" \ --include="go.mod" --include="*.yaml" --include="*.yml" --include="*.toml" # Filenames find . -name "*<term>*" -not -path "./node...

Details

Author
m0n0x41d
Repository
m0n0x41d/haft
Created
6 months ago
Last Updated
today
Language
Go
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

scrutinize

Outsider-perspective end-to-end review of a plan, PR, or proposed change — questions intent first (is there a simpler way?), then traces the actual code path (not just the diff) to verify the change does what it claims. Use BEFORE committing to an implementation, or BEFORE merging a PR — pairs with `/review-ai` (scope-question vs diff-local). Output is concise, actionable, with rationale per finding. Maps to H5 (Understand First — outsider lens) + H8 (Find Your Voice — question whether the change should exist).

3 Updated 2 days ago
pitimon
AI & Automation Listed

scrutinizing-projects

Use when asked to critique, audit, or review a codebase for architectural rot, accumulated residues, unclear naming, suboptimal design, or fitness as a base for future extension. Produces a single critique file plus a chat TL;DR. Triggers include "review my project", "audit this codebase", "is this well structured", "find tech debt", "code smells", "should we rewrite", "is this a good base for X".

0 Updated today
juliuswiener
Data & Documents Listed

code-ultrareview

Eight-axis judgment code review for the current diff — Correctness, Simplification, Tests, Documentation, Style, Intent, Design/API, Performance (+ Coherence on metadata changes). Five-phase pipeline scope → deterministic tool battery (npx/uvx-preferred, zero-install for the JS + Python majority) → 8 parallel LLM axis reviewers → Haiku validators on sub-80 findings (verbatim rubric, ≥80 threshold) → synthesis with no-silent-drop + Conventional Comments JSONL. Every report closes with "What I did NOT check" (security → /security-review, runtime perf, flaky detection). Opt-in flags `--verify-build`, `--mutation-test`, `--reconcile`, `--apply-safe`. Public-skill posture — zero auto-install, graceful skip on missing native tools.

2 Updated today
coroboros