alexei.dolgolyov
8651767112
Adds bot commands for the bridge_self provider so operators can inspect and manage bridge health from chat: /status, /thresholds, /reset, /health. Includes Jinja2 templates for both locales, seed data, capability slots, and a handler that exposes pending deferred backlog plus per-counter reset. Also adds .claude/skills/ for project-scoped graph-aware skills.
30 lines
1.0 KiB
Markdown
30 lines
1.0 KiB
Markdown
---
|
|
name: Review Changes
|
|
description: Perform a structured code review using change detection and impact
|
|
---
|
|
|
|
## Review Changes
|
|
|
|
Perform a thorough, risk-aware code review using the knowledge graph.
|
|
|
|
### Steps
|
|
|
|
1. Run `detect_changes` to get risk-scored change analysis.
|
|
2. Run `get_affected_flows` to find impacted execution paths.
|
|
3. For each high-risk function, run `query_graph` with pattern="tests_for" to check test coverage.
|
|
4. Run `get_impact_radius` 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.
|