CtrlK
BlogDocsLog inGet started
Tessl Logo

review-changes

Perform a structured code review using change detection and impact

60

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/review-changes/SKILL.md
SKILL.md
Quality
Evals
Security

Review Changes

Perform a thorough, risk-aware code review using the knowledge graph.

Steps

  1. Run detect_changes_tool to get risk-scored change analysis.
  2. Run get_affected_flows_tool to find impacted execution paths.
  3. For each high-risk function, run query_graph_tool with pattern="tests_for" to check test coverage.
  4. Run get_impact_radius_tool to understand the blast radius.
  5. For any untested changes, suggest specific test cases.

Output Format

Provide findings grouped by risk level (high/medium/low) with:

  • What changed and why it matters
  • Test coverage status
  • Suggested improvements
  • Overall merge recommendation

Token Efficiency Rules

  • ALWAYS start with get_minimal_context(task="<your task>") before any other graph tool.
  • Use detail_level="minimal" on all calls. Only escalate to "standard" when minimal is insufficient.
  • Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
Repository
tirth8205/code-review-graph
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.