GitLink Research Reproducibility End-to-End Workflow

中文说明

This repository is the independent submission repository for GitLink CLI Competition 2026, Subtrack 3: end-to-end automated workflow.

The project implements a reproducible workflow for auditing research repository reproducibility on GitLink. It collects repository metadata and collaboration signals through gitlink-cli, combines them with local checkout evidence, scores the repository from 0 to 100, and generates reviewable Markdown and JSON outputs.

Competition Scope

Submitted track: Subtrack 3, end-to-end automated workflow.

The workflow uses five GitLink CLI command families in authenticated mode:

gitlink-cli repo +info
gitlink-cli repo +tree
gitlink-cli issue +list
gitlink-cli pr +list
gitlink-cli release +list

This exceeds the Track3 requirement of at least three CLI or Skill calls.

What It Produces

For each target repository, the workflow generates:

A reproducibility score from 0 to 100.
A Markdown audit report.
A JSON summary.
A local Issue draft for follow-up tracking.
A command log for reviewer verification.
A --fail-under threshold gate for automated acceptance.

Repository Layout

.
|-- examples/workflows/research-reproducibility-assistant/
|   |-- scripts/      # workflow script and demo runners
|   |-- tests/        # automated tests
|   |-- docs/         # architecture, runbook, reviewer guide
|   `-- examples/     # fixtures and checked-in output evidence
|-- evidence/         # preflight and review evidence
`-- submission/       # platform-facing description, evidence, and checklist

The repository contains many Markdown files because this is a workflow submission: reviewers need executable scripts, evidence, architecture notes, run instructions, and platform-facing documentation. The executable implementation is under examples/workflows/research-reproducibility-assistant/scripts/, with tests under examples/workflows/research-reproducibility-assistant/tests/.

Verified Evidence

Authenticated GitLink CLI run: gitlink-cli 0.2.0, user ZorIgn.
Real target repository: official Gitlink/gitlink-cli.
Real authenticated mode score: 53/100.
Recorded real CLI command events: 10.
Default local demo score: 96/100.
Positive-control fixture score: 96/100.
Automated tests: 6 passed.
Robust preflight: 10 passed, 0 skipped.

Quick Verification

cd examples\workflows\research-reproducibility-assistant
python -m py_compile .\scripts\research_reproducibility.py .\tests\test_research_reproducibility.py .\tests\test_output_artifacts.py .\tests\test_high_evidence_fixture.py
python -m pytest -q -p no:cacheprovider tests
powershell -ExecutionPolicy Bypass -File .\scripts\run_demo.ps1 -FailUnder 70

Expected result:

6 passed
score=96/100 grade=A - strong reproducibility evidence
Workflow output validation passed: outputs

Key Evidence Files

Authenticated CLI output: examples/workflows/research-reproducibility-assistant/examples/real_gitlink_outputs/
Positive-control output: examples/workflows/research-reproducibility-assistant/examples/high_evidence_outputs/
Demo evidence document: submission/demo-evidence.md
Platform description: submission/competition-entry.md
Final submission index: submission/final-submission-index.md
Web submission checklist: submission/final-web-submit-checklist.md

Remote Write Policy

The workflow performs read-only collection by default. Remote Issue creation is intentionally left outside the automated audit path and should only be executed after a human reviews the generated local Issue draft.