skills.rest
evanfang0054
evanfang0054COMMUNITY
Explore all skills by this author →
GitHub

computational-sensors

Run linting, type checking, testing, and coverage sensors before code analysis.

Updated Apr 1, 2026
Search Tags:#code quality#testing#linting#type checking#computational sensors
One-click install
npx skills add https://github.com/evanfang0054/agent-harness --skill computational-sensors
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: computational-sensors
Source: https://github.com/evanfang0054/agent-harness/tree/main/skills/computational-sensors
Command: npx skills add https://github.com/evanfang0054/agent-harness --skill computational-sensors

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Computational Sensors address the challenge of verifying the quality of code before deeper semantic analysis.

Core Features & Use Cases

  • Preventive Code Review: Execute deterministic checks such as linting, type-checking, testing, and coverage to ensure code passes before a deeper review.
  • Task-Specific Sensors: Run various sensors in order including lint, typecheck, test, and coverage for comprehensive verification.
  • Customizable: Configure only the necessary sensors in the project's .agent-harness/sensors.json file for a tailored approach.

Quick Start

To perform computational sensors on a project, first run the following command in the project directory:

./run-sensors

Frequently Asked Questions about computational-sensors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run linting and type checking before a code review?▼

Linting and type checking run as deterministic computational sensors via the `./run-sensors` command, executing task-specific checks to verify code quality before deeper semantic analysis.

What is the best way to automate testing and coverage checks at build-time?▼

Automating testing and coverage at build-time is handled by executing computational sensors in sequence, ensuring deterministic verification passes before deeper code analysis begins.

Can I configure which code quality sensors run for my project?▼

Code quality sensors are customizable by configuring only the necessary checks, such as lint, typecheck, test, and coverage, in the project's `.agent-harness/sensors.json` file.

Does this tool require any external dependencies to run pre-commit checks?▼

No external dependencies are required to run pre-commit checks; the computational sensors operate independently using the included scripts component to execute deterministic verifications.

Why run deterministic checks before semantic code analysis?▼

Deterministic checks like linting and type checking run before semantic analysis to preventively verify code quality, catching structural errors early before deeper review processes.

When should I use computational sensors in my development workflow?▼

Use computational sensors during pre-commit or build-time development workflows to execute deterministic checks like testing and coverage, ensuring code passes verification before review.

Related Skills

Explore More Software Engineering Skills→
tuanemuytuanemuy

implement-test

Delegate test implementation to sub-agents and orchestrate review cycles.

Community
Advanced
Sake-TeamSake-Team

verification-loop

Automates multi-phase verification for Claude Code sessions before commits or PRs.

Official
Advanced
x-meshx-mesh
1

build

Automate build script execution for software development workflows.

Official
Intermediate
joyce820309joyce820309

health

Generate a weighted 0-10 score for codebase quality from tool outputs.

Community
Intermediate