ECP Time Report Auto-Filling

Extract the day's commit descriptions from the release branches of

springcloud-aile

and

AuthServer\authserver

, automatically generate and submit them to ECP time reports.

Configure First After Installation

Double-click the

configure-ecp-timereport.cmd

(shortcut) or run

python scripts/configure_timereport.py --interactive

Write the following variables into
```
config/timereport-config.json
```
(no longer strongly dependent on environment variables):
- Local project mappings (
```
name + path
```
  , supports multiple entries)
- ECP account/password
- Optional time report extensions (total working hours, Git author filtering, output directory, etc.)
When saving the configuration for the first time, the current device fingerprint will be automatically recorded in
```
device_binding
```
.
You can run the shortcut script repeatedly later to update the configuration at any time.

Conversational Configuration Completion Process

When the user says "fill today's time report", "submit today's time report", "backfill time report", etc., the following process must be enforced:

First run

python scripts/configure_timereport.py --show-required-status

to check the status of required configurations.

If
```
ready=true
```
, proceed to execute the filling script.
If
```
ready=false
```
, do not end directly, nor just let the user run the script on their own.
Must actively request the missing fields from the user in the current conversation, only ask for items in
```
missing_fields
```
:
- ```
projects
```
  : Ask the user to provide local repository paths in the format
```
name=path;name=path
```
- ```
ecp.username
```
  : Ask the user to enter the ECP account
- ```
ecp.password
```
  : Ask the user to enter the ECP password
After receiving the user's input, immediately run
```
python scripts/configure_timereport.py
```
to write the values back to
```
config/timereport-config.json
```
.

After writing back, run

python scripts/configure_timereport.py --show-required-status

again.

Only when

ready=true

can you proceed to execute

python scripts/fill_timereport.py --submit ...

Conversation Constraints:

Prioritize completing the configuration in the current conversation, do not push the responsibility back to the user to manually execute the script.
Only ask for missing items each time, do not repeatedly request existing values.
If the project path can be inferred from the most recent time report or the current workspace, reuse it first, then only ask the user for the remaining missing items.
After writing the configuration, briefly inform the user "Configuration completed, proceeding to submit the time report" before continuing with the filling.

Built-in Filling Rules

Only perform filling on legal working days in mainland China (including adjusted workdays), no filling on holidays/rest days.
When there are multiple commits on the same day, only take the earliest commit description as the day's time report description.
When there are no commits on the day, automatically search for dates with "multiple commits" in adjacent dates, and prioritize selecting the commit record that has not been filled yet.
If there are no "multiple commits" in adjacent dates or all these records have been filled, do not fill the day's report for now, and re-judge during the next execution; only use vague descriptions to automatically fill during month-end backfilling (e.g., optimize related code, adjust related business logic, cooperate with front-end to adjust interfaces).
When executing
```
--submit
```
on the day, it will automatically check for missing time reports in past working days of the month and backfill them; if
```
--activity-detail
```
is used to manually specify leave/meetings, only process the target date and do not trigger full-month backfilling.

--activity-type 休假 --activity-detail 特休假

will generate the description

Leave - Special Leave

and will not be associated with tasks.

--activity-type 会议 --activity-detail 顾问会议

will generate the description

Meeting - Consultant Meeting

and will keep the task association.

The progress percentage in the time report details is uniformly set to
```
100%
```
(consistent for the first working day of the month and subsequent working days).
When triggering the skill, it will first verify
```
device_binding.fingerprint
```
; if it is missing or inconsistent with the current device, it will automatically clear the business variables in the configuration file, only retain the current device fingerprint and blank required items, and then must request the user to complete
```
projects
```
,
```
ecp.username
```
,
```
ecp.password
```
according to the "Conversational Configuration Completion Process".

Workflow

Read the local project mappings and ECP parameters from
```
config/timereport-config.json
```
.
After logging into ECP, first call
```
Ecp.Aile.getOnlineUser
```
to obtain the current
```
userId
```
.
Then call
```
Ecp.TimeReport.getAllRelevantObjs
```
to automatically match the month's task
```
taskId
```
.
If required configurations are missing, first complete the configuration according to the "Conversational Configuration Completion Process", then proceed.
Run
```
scripts/fill_timereport.py
```
to extract the day's commits from the release branch and generate the time report content.
Check the JSON report generated under
```
timereport-reports/
```
.
Use
```
--submit
```
to write to the ECP time report.

Cross-Device Protection Process

After the skill is successfully configured for the first time, the current device fingerprint will be written to
```
device_binding
```
in
```
config/timereport-config.json
```
.
Before each run of
```
scripts/fill_timereport.py
```
, the fingerprint will be verified.
If the fingerprint is missing or inconsistent with the current device, the script will automatically clear the business variables in the configuration.
Do not terminate directly at this point; you must request the user to complete
```
projects
```
,
```
ecp.username
```
,
```
ecp.password
```
through the current conversation.
After receiving the user's input, run
```
python scripts/configure_timereport.py
```
to write the new values back to the configuration, and the script will re-write the new device fingerprint into the configuration.

Command Examples

bash

# Generate only, do not submit
python scripts/fill_timereport.py

# Specify date
python scripts/fill_timereport.py --date 2026-03-11 --branch release

# Specify leave (not associated with tasks)
python scripts/fill_timereport.py --date 2026-03-13 --activity-type 休假 --activity-detail 特休假 --submit

# Specify meeting (associated with tasks)
python scripts/fill_timereport.py --date 2026-03-16 --activity-type 会议 --activity-detail 顾问会议 --submit

# Submit to ECP (default 8 hours)
python scripts/fill_timereport.py --submit

# Specify configuration file
python scripts/fill_timereport.py --config .\config\timereport-config.json --submit

# Quick configuration modification (command line)
python scripts/configure_timereport.py --projects "project-a=/path/to/project-a;project-b=/path/to/project-b" --username "your-username" --password "your-password"

Configuration Source Priority

Preferred:
```
config/timereport-config.json
```
Compatible: Command line parameters (highest priority) and historical environment variables (fallback)

Failure Handling

When there are no commits on the specified date, it will try the "adjacent multiple commits" or "month-end vague backfilling" strategy.
If there is already a time report detail for the day, it will terminate by default; add
```
--allow-overwrite
```
to continue.
If an ECP interface error occurs, retain the JSON report and return a non-zero exit code.

References

See
```
references/setup.md
```
(environment configuration and automation templates).

ecp-timereport-autofill

NPX Install

Tags

SKILL.md Content (Chinese)