docs(skill): distinguish submit-time from add-time in PR lifecycle

[zolotokrylin]

Summary

• Teach the /submit-time command both Wizard bot forms: `pr submit-time ` (overwrite total) vs `pr add-time ` (add on top of a previous submission)

Context

The /submit-time command posted the wrong syntax on a PR because it only knew about `pr submit-time`, not the separate `pr add-time` command.

• Closes #120

Test plan

• Confirm the command's accepted syntax matches the Wizard bot's actual behavior

[holdex]

Time Submission Status

Member	#	Time	Running Total	Status	Last Update
zolotokrylin			16min	✅ Submitted	Jul 7, 2026, 8:14 AM

---

Submit or update total time with:

@holdex pr submit-time 2h

Add time on top of previous submission with:

@holdex pr add-time 1h30m

See available commands to help comply with our Guidelines.

[coderabbitai]

Walkthrough

This PR updates documentation only: .claude/commands/submit-time.md clarifies input parsing rules distinguishing add-prefixed from non-add time arguments, and splits the posted comment template into two variants (submit-time/add-time). docs/CONTRIBUTING.md adds matching Wizard bot command examples to the PR lifecycle checklist.

Changes

Time reporting documentation

Layer / File(s)	Summary
Submit-time command input and posting logic .claude/commands/submit-time.md	Input section now documents add-prefixed vs non-add behavior, accepted time formats, and empty-argument prompting; posting instructions split into separate submit-time <TIME> and add-time <TIME> comment templates.
Contributor lifecycle documentation docs/CONTRIBUTING.md	PR Lifecycle checklist step for reporting time now includes explicit @holdex pr submit-time and @holdex pr add-time bot command examples.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related issues

• holdex/developers#120: Addresses the same submit-time vs add-time documentation/command confusion.

Possibly related PRs

• holdex/developers#113: Also modifies .claude/commands/submit-time.md, adding submit-time command documentation and accepted time-format rules.

Suggested reviewers: markholdex

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The docs now document both pr submit-time and pr add-time where contributors see them, matching #1588's requirement.
Out of Scope Changes check	✅ Passed	Changes stay within documentation updates for PR time reporting and the command guidance; no unrelated code changes appear.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the docs update to distinguish submit-time from add-time in the PR lifecycle.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/submit-time-add-time-commands

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[zolotokrylin]

@holdex pr submit-time 16m