Still Copy‑Pasting Bugs? This Skill Inserts Bugs into Feishu Base in 10 Seconds

Background

bug‑report‑writer v1.0 reduced the time to create a bug report from 12‑15 minutes to about 2 minutes, a six‑fold efficiency gain.

Problem prompting v1.1.1

After generating a markdown bug report, engineers still needed to copy‑paste the data into different bug‑tracking tools (Zentao, TAPD, Feishu Base) because field names differed, causing repetitive manual alignment.

v1.1.1 Enhancements

Feishu Base one‑click write – uses the Feishu API to insert a bug directly, completing in 10‑15 seconds.

Automatic field mapping – reads the Feishu table schema and matches fields intelligently, removing manual alignment.

Batch processing – can generate and import 5‑20 bugs in a single operation.

Six‑dimension quality scoring – evaluates bugs on reproduction steps (25), expected/actual result (20), environment info (15), severity (15), attachment completeness (15), and title quality (10). Total score 100, pass threshold 60; scores below 60 trigger a rewrite suggestion.

Feishu Base workflow

The Feishu multidimensional table contains nine fields: Reporter, Title, Description, Steps, Priority, Type, Status, Owner, Screenshot.

v1.0 workflow :

1. bug‑report‑writer generates markdown<br>2. Open Feishu table<br>3. Manually copy each field, align names<br>4. Upload screenshot<br>5. Submit

Typical duration: ~5 minutes per bug (5 bugs → 25 minutes).

v1.1.1 workflow :

1. Send screenshot and description to bug‑report‑writer<br>2. Tool extracts error info, generates a standard bug report, reads Feishu fields, performs smart matching, writes via API<br>3. Bug appears in Feishu table after ~10 seconds

Batch import of five bugs completes in about ten seconds.

Efficiency comparison (real‑world test)

Manual write + Feishu entry

Time: 12 minutes. Operations: screenshot 3 min, description 3 min, grading 2 min, Feishu entry 3 min, extra investigation 1 min.

bug‑report‑writer v1.0

Time: 2 minutes. Operations: screenshot + description 10 s, AI generation 30 s, manual review 1 min, copy‑paste 20 s.

bug‑report‑writer v1.1.1

Time: 10‑15 seconds. Operations: screenshot + description 10 s, AI generation, smart field matching, API write.

Speedup: 48‑72× versus manual, 8‑12× versus v1.0.

Five‑bug afternoon: manual 60 min, v1.0 10 min, v1.1.1 1 min.

Monthly (20 workdays × 5 bugs): manual 100 h, v1.0 16.7 h, v1.1.1 1.7 h – saving ≈ 98 h (≈ 12 workdays).

Supported bug‑management platforms

Feishu Base – API one‑click write (10‑15 s).

Zentao – generates markdown in Zentao format for manual copy‑paste.

TAPD – generates TAPD‑format markdown for manual copy‑paste.

Jira – generates Jira‑format markdown for manual copy‑paste.

Markdown – generic markdown for chat or PDF.

JSON – standard bug‑report protocol ( bug-reports/standard/v1) for toolchain integration.

Usage

Install WorkBuddy.

Install bug‑report‑writer v1.1.1.

Authorize Feishu via lark-cli on first run; the tool auto‑detects the table schema.

For each bug, send screenshot and description to the skill; the bug appears in the Feishu table after ~10 seconds.

Future work

API one‑click write for Zentao (research stage).

API one‑click write for TAPD.

API one‑click write for Jira.

Conclusion

v1.0 solved “how to write a bug” (12 min → 2 min). v1.1.1 solves “how to push a bug into Feishu” (2 min → 10 s). Automating fixed‑format entry lets engineers focus on bug validation and severity assessment.