Analyze test quality for semantic correctness before pull requests.
npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-test-review
Please help me install this Agent Skill. Skill: dev-test-review Source: https://github.com/Obsidian-Owl/agentlint/tree/main/.claude/skills/dev.test-review Command: npx skills add https://github.com/Obsidian-Owl/agentlint --skill dev-test-review
This skill provides semantic analysis of test quality prior to PRs, ensuring tests align with agentic coding principles and governance.
High-intent search queries and answers about installing and using this skill.
To ensure test quality before a PR, you can run a semantic test analysis on changed files to evaluate purpose, correctness, isolation, and maintainability. This acts as a quality gate to enforce agentic coding compliance.
The best way to audit VCR integration and TruLens eval tests is to run a full repository audit. This validates test type appropriateness and enforces ADR-0011 and ADR-0012 compliance across all files.
Yes, semantic test analysis checks alignment with ADR-0011 and ADR-0012 governance standards. It validates that unit, VCR, and eval tests comply with these architectural decisions and produces actionable recommendations.
Yes, you can review the test design quality of a specific file by targeting it directly. This per-file review evaluates semantic correctness and maintainability without scanning the entire repository.
To validate that unit tests are properly isolated for agentic code, run a semantic analysis check. This evaluates test isolation and overall design quality to ensure alignment with agentic coding principles.
Obsidian-OwlSelect unit tests, VCR integrations, or TruLens evals for agentic code.
doanchienthangdevEnforce quality gates, clean Git history, and prepare pull requests.
pradyumnasagarAutomate inter-skill data transfer and provenance capture via JSON Material Passports.
R2W1csLint and validate JavaScript and Python code for syntax and style issues.
