From ctx-customer-pack
Change confidence tools: get_change_confidence, get_file_risk_factors
npx claudepluginhub codota/ctx-customer-pack-distributable --plugin ctx-customer-packThis skill is limited to using the following tools:
> Auto-generated from 2 exported tool(s) in the Context Engine.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Auto-generated from 2 exported tool(s) in the Context Engine.
Calculate a confidence score for a proposed code change. Aggregates multiple risk signals into a single 0-100 score: - File risk metrics (churn, bug-fix ratio, hotspot status) - Blast radius (direct/transitive dependents, critical services) - Historical incidents (past issues in affected areas) - Code coupling (files that change together) - Expert coverage (knowledge concentration risk) Score interpretation: - 90-100 (GREEN): Low risk, safe to merge - 75-89 (YELLOW): Moderate risk, review carefully - 50-74 (ORANGE): High risk, extensive testing needed - 0-49 (RED): Critical risk, escalation recommended USE THIS BEFORE: Merging PRs, committing significant changes, deployments Example: get_change_confidence(files=["src/payment/processor.ts", "src/payment/api.ts"])
Call mcp__tabnine-ctx-cloud__get_change_confidence with parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| files | array | Yes | List of file paths being changed (relative to repository root). Example: ["src/payment/processor.ts", "src/checkout/cart.ts"] |
| repository | string | No | Repository name for scoping queries. Optional but recommended for accuracy. |
| changeType | string | No | Type of change: "feature", "bugfix", "refactor", "dependency", "config". Affects scoring weights. Default: auto-detect from files. |
Get detailed risk analysis for a single file. Returns all risk signals contributing to the file's risk score: - Churn metrics (change frequency, commit count) - Bug-fix ratio (% of commits that are fixes) - Author analysis (expert count, knowledge concentration) - Historical incidents linked to this file/service - Coupling analysis (files that change together) USE THIS WHEN: You want detailed breakdown for a specific file rather than an aggregate score for multiple files.
Call mcp__tabnine-ctx-cloud__get_file_risk_factors with parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| filepath | string | Yes | File path to analyze (relative to repository root). |
| repository | string | No | Repository name for scoping. Optional. |