ibank-worklog-duplicate-audit

Audits iBank worklog datasets for duplicate entries and generates review packets.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-worklog-duplicate-audit-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ibank-worklog-duplicate-audit
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/ibank-worklog-duplicate-audit
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-worklog-duplicate-audit-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually reviewing large sets of iBank worklogs to identify duplicate entries, same-task duplicates, or suspicious same-title pairs is time-consuming and prone to human error, especially for team leads managing multiple contributors.

Core Features & Use Cases

  • Duplicate Detection: Automatically flags exact duplicate worklog rows, same-task duplicate entries, and suspicious same-title worklog pairs for review.
  • Lead Review Routing: Sends all suspicious worklog pairs exclusively to team leads for judgment, ensuring no unvetted changes are made to worklog data.
  • Minimal Fix Generation: For pairs marked for revision, creates minimal clarification revision JSON and updated SQL seed files to resolve ambiguities without overwriting original data.
  • Use Case: For example, if your iBank team has 3 worklogs with the title "Fix payment gateway timeout" submitted by the same engineer on the same day, this skill will flag them as a suspicious pair, route them to the team lead for a same-task/distinct/revise judgment, and generate a minimal edit to clarify the entries if needed.

Quick Start

Use the ibank-worklog-duplicate-audit skill to audit your iBank worklog entries for exact duplicates, same-task duplicates, or suspicious same-title pairs and receive team-lead-ready judgment packets with optional minimal clarification fixes.

Frequently Asked Questions about ibank-worklog-duplicate-audit

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

FAQPage Schema
How do I detect duplicate worklog entries in a large dataset?

To audit worklog duplicates, the system identifies exact duplicate rows, same-task duplicate entries, and suspicious same-title worklog pairs. It then generates duplicate-audit review packets for team leads to judge whether entries are same-task, distinct, or need revision.

What is the best way to route suspicious worklog pairs for team lead review?

Routing suspicious worklog pairs for team lead review involves flagging exact duplicates and same-title entries, then sending them exclusively to leads for judgment. This ensures no unvetted changes are made to worklog data.

Can I generate SQL seed files for confirmed duplicate worklog revisions?

Yes, you can generate updated SQL seed files for confirmed revision candidates. The system creates minimal clarification revision JSON and updated SQL seed files to resolve ambiguities without overwriting original worklog data.

How does same-task judgment work for suspicious worklog pairs?

Same-task judgment works by routing flagged worklog pairs to team leads who determine if entries are identical, distinct, or require revision. This workflow maintains worklog data quality by preventing unvetted modifications.

What types of duplicates can an iBank worklog audit identify?

An iBank worklog audit identifies exact duplicate rows, same-task duplicate entries, and suspicious same-title worklog pairs. These flagged pairs are compiled into review packets for team lead evaluation and data quality control.