reconcile
SolidUse this skill when the user wants to reconcile learnings into rules, run /reconcile, propose rules from learnings, turn learnings into .claude/rules/ entries, or review what rules would be generated from current session learnings. On-demand version of session-end Phase 3.6.8.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- Kanevry
- Repository
- Kanevry/session-orchestrator
- Created
- 3 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
data-reconcile
Reconcile any two record sets (A vs B) and triage the discrepancies — match line-by-line on a shared key, or heuristically on amount + date, then classify every unreconciled item (category, materiality, probable cause, suggested action) into a reconciliation working paper (.xlsx). Use whenever the user wants to "reconcile A to B", "reconcile the bank to the ledger", "reconcile the invoice tracker to the accounts", "tie out", "match these two lists/exports", "find the differences between", "what doesn't match", "reconciliation working paper", or "discrepancy triage". Ships presets for common recurring reconciliations (invoice tracker vs accounting records, bank vs cashbook, fund administrator vs internal records, payments/PRF vs bank); generic for anything else. Deterministic and computed locally — it never force-fits a match and never posts an adjustment; it produces a working paper for finance to review and sign off. NOT budget/variance analysis, and NOT deal/asset analysis (that is out of scope).
pm-reconcile
Rebuild playbook for an existing product onboarded to Pureinn. Reconciles the actual codebase against a folder of legacy documents (BRD, FSD, domain/entity models, business rules) that may contain logical, semantic and structural inconsistencies. Runs in two phases - first PLAN (inspect docs + code, define which areas to reconcile, in what order, into which Pureinn artifacts), then per-area EXECUTION (/pm-reconcile domain | rules | features ...) one layer at a time. Produces a living Reconciliation Report and rebuilds the 4 Live Registers + feature inventory clean. A closing verify pass (/pm-reconcile verify) re-reads the source one last time, proves every unit was transposed, incorporates any gaps it finds (not just reports them), and rules whether the legacy source is safe to archive - the source-disposal gate. The source is whatever the user points to (any format), never a hardcoded BRD. Use when a product was built outside the framework, has stale or conflicting docs, and the (often new) team needs one co
agami-reconcile
Reconciles known (label, expected_value) numbers from an existing dashboard against agami's answers. Input can be a SCREENSHOT of a Metabase / Power BI / Tableau / Looker dashboard (Claude's vision extracts the pairs), a CSV, or numbers pasted inline — the user doesn't need to know which; they can just ask. For each pair, the skill generates a matching NL question, runs it through the active profile's semantic model, diffs actual vs expected, and surfaces matches in green and mismatches in red with drill-down receipts. The strongest onboarding demo for a skeptical data engineer — either we agree with their numbers (trust earned via evidence) or we surface a real definitional disagreement (trust earned via transparency).