ifixkart-admin/.agents/skills/feature_impact_analysis/SKILL.md
Adithiyan bbd3a3e959 feat: initial commit — full platform snapshot
- Backend: FastAPI app with all models, services, schemas, routes
- Admin Panel: Next.js dashboard with all modules
  (CRM, POS, repairs, warranties, billing, notifications, etc.)
- Ecommerce: storefront (submodule) + product catalog
- AI Agents: .agents/ skill library for Antigravity IDE
- Docs: architecture, billing, notification gateway markdown
- Submodules: Backend/OpenWA, Ecommerce/File 2/storefront
2026-10-13 12:59:47 +05:30

31 lines
1.5 KiB
Markdown

---
name: "Feature Impact Analysis"
description: "Analyzes system dependencies to evaluate how code changes impact other modules, labeling impact as High, Medium, or Low."
---
# Skill: Feature Impact Analysis
## 1. Purpose
Identify potential regressions or side effects of code changes by mapping dependencies across the iFixKart stack.
## 2. When to Use
Run before drafting any implementation plan for files affecting core APIs, DB schemas, or reusable components.
## 3. Preconditions
* Target file dependencies are identified via context optimizer and graphify.
## 4. Step-by-Step Checklist
1. List all source files scheduled for modification.
2. Search for references to these files/modules across:
- React components and frontend layouts.
- FastAPI routers, route parameters, and controllers.
- Pydantic schemas and SQLAlchemy models.
- Database tables, columns, indexes, and views.
- Analytics (PostHog), Dashboards, and Reports.
- Background workers and celery tasks.
- Unit, integration, and E2E tests.
3. Label the impact risk:
- **HIGH IMPACT**: Modifying base database schemas, shared auth middleware, core API schemas, or major layout structures.
- **MEDIUM IMPACT**: Adding fields to local API models, changing specific page components, or modifying utility functions.
- **LOW IMPACT**: Updating logs, documentation, writing unit tests, or changing comments.
4. Document the dependency chain and impact labeling in the implementation plan.