dream-num/dogfooding · Archived

univer-worklog-auto

Use when the user wants to automatically collect Codex/workbuddy/git/GitHub evidence, summarize work, dedupe it, and write or dry-run Univer worklog rows. Supports --dry-run, --confirm, --no-submit, and --period day|week|month.

First seen May 20, 2026

Installation

$ npx skills add dream-num/dogfooding --skill univer-worklog-auto

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from dream-num/dogfooding.

npx skills add dream-num/dogfooding

Browse all from dream-num/dogfooding

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,848 B
  • docs SUMMARY.md 254 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

univer-worklog-auto

Use the core protocol in ../univer-team-standup/SKILL.md, route intent auto.

Support:

  • univer-worklog-auto
  • univer-worklog-auto --dry-run
  • univer-worklog-auto --confirm
  • univer-worklog-auto --no-submit
  • univer-worklog-auto --period day|week|month

Follow the core Auto workflow exactly: bootstrap Univer dependencies if missing, enforce the mandatory team remote fYmh0HRyTUO6YECQGFScnA0 on https://univer.ai/, collect evidence, summarize, resolve priority through WorkItems, dedupe with 去重键, write allowed rows, verify by reading back, audit, preview, and auto-submit when the Team Auto Submit policy allows it. Auto must re-check the bound unit id before pull, before writing, before commit/sync, and after sync; if the target cannot be proven as fYmh0HRyTUO6YECQGFScnA0, stop before syncing. Always follow the core Personal Log Date Field Policy: write 日期 as the local work date, apply yyyy-mm-dd display formatting, and verify the date display is not a naked spreadsheet serial number. Always follow the core Progress And Risk Prompting Policy: infer progress, risk, blocker, plan, and next-action fields from evidence when possible, and surface missing items as 需补充 or 待确认 before writing.

During 2026-05-21 through 2026-06-18, apply the core Business Goal Tracking rules when summarizing candidates. If evidence clearly maps to an O1-O4 KR, use goal-aware 关联项 or WorkItems hints; if uncertain, leave the candidate unmapped and let reports surface the possible focus drift.