skills.rest
Technikhighknee
TechnikhighkneeCOMMUNITY
Explore all skills by this author →
GitHub

preview

Predict type errors, affected callers, and required tests before code edits.

Updated Aug 23, 2026
Search Tags:#preview#preflight#tests#callers#type-errors
One-click install
npx skills add https://github.com/Technikhighknee/agent-workbench --skill preview
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: preview
Source: https://github.com/Technikhighknee/agent-workbench/tree/main/.claude/skills/preview
Command: npx skills add https://github.com/Technikhighknee/agent-workbench --skill preview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Predict type errors, affected callers, and required tests before making a change.

Core Features & Use Cases

  • Preflight check: Type errors and caller impact before edits.
  • Test selection: Identify related tests to run after change.
  • Risk assessment: Understand potential impact and required follow-ups.

Quick Start

preview_edit({ file: 'src/api.ts', edit_type: 'symbol', symbol: 'fetchUser', new_content: 'async function fetchUser(id: string, options?: RequestOptions): Promise<User> { ... }' })

Frequently Asked Questions about preview

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

FAQPage Schema
How do I predict type errors before editing a function signature?▼

Type error prediction identifies compilation failures caused by signature changes before you apply edits. Preview analyzes static types across your codebase to surface breaking changes to return types, parameters, and generics, so you catch mismatches early.

Can I see which callers will break when I refactor an API?▼

Yes. Preview extracts the call graph to map all call sites affected by your edit, showing exactly which functions, modules, and external dependencies depend on the symbol you're changing so you understand propagation reach.

What tests should I run after changing a function?▼

Test mapping identifies related tests by correlating test coverage to call graph data, surfacing which test suites exercise the changed symbol and its dependents so you run only the tests that validate the change.

How do I assess the risk of an API refactor?▼

Risk assessment combines type errors, caller count, and test coverage into an impact report that quantifies breaking scope, affected surfaces, and test implications, helping you decide whether to proceed or restructure the change.

Does preview work with TypeScript and JavaScript edits?▼

Preview performs static analysis on typed symbols and signatures, working most effectively with TypeScript where type information is explicit. JavaScript support depends on available type hints and call graph inference accuracy.

What happens if a change has no callers or tests?▼

Preview still reports type errors and identifies orphaned symbols with zero callers or test coverage, flagging low-risk but potentially untested changes so you make informed decisions about deprecation or removal.

Related Skills

Explore More Software Engineering Skills→
mscipiomscipio

ast-analyzer

Parse source code into Abstract Syntax Trees for symbol extraction and variable flow tracing.

Community
Advanced
JiggerFJiggerF

pr-impact-test

Map PR diff files to affected test suites and run targeted vitest commands.

Community
Advanced
reomgitreomgit

health

Compute a weighted composite code quality score from project tools.

Community
Advanced
ClyptAIClyptAI

gitnexus-impact-analysis

Map code change dependencies and generate risk reports before edits.

Official
Intermediate