← ClaudeAtlas

india-tax-gurulisted

India income-tax planning, salary/CTC restructuring, and ITR-1/2/4 filing-support toolkit for individuals and HUFs. Computes old-vs-new regime comparison, HRA/capital-gains/house-property tax, presumptive business and professional income (s.44AD/44ADA), GST-turnover reconciliation for presumptive filers, advance-tax interest (234B/234C), and optimal CTC splits. Triggers on: India income tax, ITR-1/ITR-2/ITR-4, old vs new tax regime, HRA exemption, CTC structuring/salary restructuring, take-home salary, capital gains tax India, US stocks or foreign-listed RSU sale, freelancer or consultant tax India, shop/small-business presumptive tax, 44AD, 44ADA, GST turnover vs ITR mismatch, HUF taxation, section 87A rebate, Form 16/payslip reconciliation, Form 10-IEA, or advance tax interest questions.
anivar/india-tax-guru · ★ 1 · API & Backend · score 75
Install: claude install-skill anivar/india-tax-guru
# india-tax-guru A computation engine, not a chat-only assistant — every claim it makes about tax owed traces back to a specific function in this repo, and every rule is versioned per assessment year so nothing drifts silently across Budgets. ## When to use this skill - User asks which tax regime (old vs new) is better for their income/deductions. - User wants their CTC restructured (Basic/HRA/employer-NPS split) to maximize take-home pay. - User wants HRA exemption, capital gains tax, or house-property income/loss computed correctly (period-wise, not a flat annual shortcut). - User wants to reconcile monthly payslips against Form 16. - User wants advance-tax interest (234B/234C) estimated. - User has presumptive business or professional income (s.44AD/44ADA), including a GST-registered filer whose ITR turnover needs reconciling against GSTR figures. - The assessee is an HUF (`assessee_type="huf"`). ## Importing documents There are no document parsers in this repo, by design — ITD publishes no schema for the prefill JSON or AIS JSON, and Form 16 Part B renders differently per payroll vendor, so a hardcoded parser fails silently. **You are the importer.** Read the document, fill in `profile.json`, and let the engine do the arithmetic. The division of labour is not negotiable: **you never compute tax.** Reading a semi-structured document you have never seen before is what you are good at; arithmetic that nobody can unit-test is what the engine is for. If you catch y