SeekDB Competition Repository Preflight

When to use

Use this skill to examine a local competition repository before submitting a branch or commit for evaluation. It helps diagnose 403, missing upstreams, unexpected branches, unstaged changes, and basic GitHub network failures. The default expected branch is 2026-competition, but the user can select another branch.

Do not use this skill to change code, upload private information, generate a competition validation line, or guarantee a passing score.

Inputs

Absolute or relative path to the user's local Git repository.
Expected branch (default: 2026-competition).
Optional reported error message from Git or the evaluation platform.

Never ask for a GitHub password or personal access token to be pasted into a chat or log.

Workflow

Confirm repository and intent. Ask which repository and branch are being evaluated if they are not already clear. Do not confuse a GitHub repository URL with a ModelScope Skill URL.
Run the read-only checker. From this Skill's directory run:
```
bash scripts/preflight.sh /path/to/repo 2026-competition
```
The first parameter is a local repository path; the second is the expected branch. The script does not fetch, stage, commit, push, or alter the repository.
Interpret the findings. Report the actual branch, current commit, working-tree state, whitespace checks, configured remotes, and upstream ahead/behind counts (if available). Warn that ahead/behind counts are based on local remote-tracking refs and may be stale.
Diagnose errors without leaking secrets.
- 403: check repository access, fork permissions, and token write permissions in the user's credential manager. Do not print or request token values.
- could not resolve host or connection timeouts: check DNS, VM networking, and whether a proxy configured in the VM is actually reachable. Do not assume a hardcoded proxy IP.
- src refspec ... does not match any: verify the branch exists and that a commit exists.
- non-fast-forward: inspect remote divergence before proposing any merge/rebase; never recommend a force push by default.
Propose the minimum next action, ask approval before any state-changing command, and never execute a push automatically.
Separate evaluation outcomes. A clean repository is not proof that a competition evaluation will pass. Quote only results that can be observed.

Output format

Provide a compact Chinese report with:

Repository and expected/actual branch
Current commit SHA
Working-tree and staged whitespace checks
Remote and upstream status (including uncertainty if not fetched)
Recommended next step with a copyable command, if action is required

Security and portability

Read only; no git push, git reset --hard, git clean, or force operations.
Never print full credential-bearing remote URLs, secret environment variables, or PATs.
On VMware/CentOS network issues, verify guest connectivity before changing proxy settings.
If the user is preparing the ModelScope Skill publishing challenge, keep that challenge's validation line at the end of this SKILL.md; it is not a GitHub README validation line.

Competition verification

The contestant must append the exact full verification line issued by the evaluation popup after this paragraph, as the final non-empty line of this file, before repackaging and publishing the public Skill. Do not guess or invent the line.