tax-evolve

Analyze /tax-compare discrepancies, classify root causes, and generate fixes for GitHub PRs.

12|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Fangyi-Chen/SuperTaxAgent --skill tax-evolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tax-evolve
Source: https://github.com/Fangyi-Chen/SuperTaxAgent/tree/main/skills/tax-evolve
Command: npx skills add https://github.com/Fangyi-Chen/SuperTaxAgent --skill tax-evolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides automatic analysis of discrepancies detected in tax workflow comparisons, classifying root causes and generating fixes to skill files and references while ensuring no sensitive data is exposed.

Core Features & Use Cases

  • Analyze mismatches produced by /tax-compare and determine root causes across the tax-evolve workflow.
  • Generate concrete fixes to skills/tax-evolve files and related references, and prepare changes for a GitHub PR.
  • Log evolution attempts to data/evolution-log.json and trigger /tax-publish when fixes are ready to be submitted.
  • Propose domain-skill scaffolds when repeat mismatch patterns indicate broader gaps (e.g., new tax domains or data structures).

Quick Start

Run /tax-compare to generate mismatches, then run /tax-evolve to propose fixes.

Frequently Asked Questions about tax-evolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tax workflow discrepancy fixes and generate a GitHub PR?

To automate tax workflow discrepancy fixes, this Skill analyzes mismatches from /tax-compare, classifies root causes, generates fixes to skill files, and submits them as a GitHub PR via /tax-publish.

How does automatic root cause analysis for tax comparison mismatches work?

Root cause analysis for tax comparison mismatches works by evaluating discrepancies found by /tax-compare, classifying their origins, and proposing concrete fixes to skill files and references while logging patterns to evolution-log.json.

What is the best way to log tax skill evolution patterns for version control?

The best way to log tax skill evolution patterns is to record them automatically in evolution-log.json, capturing each discrepancy classification and fix attempt to maintain a version-controlled history of tax workflow changes.

When do I need to scaffold new domain skills for repeat tax mismatch patterns?

You need to scaffold new domain skills when repeat mismatch patterns from /tax-compare indicate broader gaps in tax domains or data structures, allowing the evolution workflow to propose structural expansions.

Does this tax evolution workflow expose sensitive data when generating fixes?

No, the tax evolution workflow ensures no sensitive data is exposed while analyzing discrepancies, classifying root causes, and generating fixes to skill files and references for GitHub PR submission.