This repository is the independent submission repository for GitLink CLI Competition 2026, Subtrack 3: end-to-end automated workflow.
Competition Scope
The submitted work is a Track3 workflow that audits reproducibility evidence for GitLink-hosted research repositories. It combines authenticated GitLink CLI collection with a local checkout fallback, then produces reviewable reports and machine-readable outputs.
Workflow Outputs
For each target repository, the workflow generates:
Reproducibility score from 0 to 100.
Markdown audit report.
JSON summary.
Local Issue draft for follow-up tracking.
GitLink CLI command log for reviewer verification.
--fail-under gate for automated acceptance.
GitLink CLI Command Chain
Authenticated mode uses these GitLink CLI command families:
gitlink-cli repo +info
gitlink-cli repo +tree
gitlink-cli issue +list
gitlink-cli pr +list
gitlink-cli release +list
The workflow therefore uses five CLI command families, exceeding the Track3 requirement for at least three CLI or Skill calls.
Repository Layout
examples/workflows/research-reproducibility-assistant/: workflow implementation, scripts, tests, docs, fixtures, and example outputs.
evidence/: preflight and Track3 alignment evidence.
submission/: platform-facing description, demo script, final index, and checksum record.
Evidence Summary
Authenticated GitLink CLI run: gitlink-cli 0.2.0, user ZorIgn, target Gitlink/gitlink-cli, score 53/100, 10 recorded command events.
Official Gitlink/gitlink-cli local checkout demo: 77/100.
Positive-control fixture: 96/100.
Tests: 6 passed.
Robust preflight: 9 passed, 0 skipped.
Final package cleanliness: no skills/, no runtime caches, no local clone directories.
Final submission index: submission/final-submission-index.md
Remote Write Policy
The workflow performs read-only collection by default. Remote Issue creation is outside the automated audit path and requires an explicit operator command after reviewing the generated local Issue draft.
关于
Track3 end-to-end GitLink CLI workflow for research reproducibility auditing, with authenticated CLI evidence, demo outputs, tests, and submission docs.
GitLink Research Reproducibility End-to-End Workflow
中文说明:README.zh-CN.md
This repository is the independent submission repository for GitLink CLI Competition 2026, Subtrack 3: end-to-end automated workflow.
Competition Scope
The submitted work is a Track3 workflow that audits reproducibility evidence for GitLink-hosted research repositories. It combines authenticated GitLink CLI collection with a local checkout fallback, then produces reviewable reports and machine-readable outputs.
Workflow Outputs
For each target repository, the workflow generates:
--fail-undergate for automated acceptance.GitLink CLI Command Chain
Authenticated mode uses these GitLink CLI command families:
gitlink-cli repo +infogitlink-cli repo +treegitlink-cli issue +listgitlink-cli pr +listgitlink-cli release +listThe workflow therefore uses five CLI command families, exceeding the Track3 requirement for at least three CLI or Skill calls.
Repository Layout
examples/workflows/research-reproducibility-assistant/: workflow implementation, scripts, tests, docs, fixtures, and example outputs.evidence/: preflight and Track3 alignment evidence.submission/: platform-facing description, demo script, final index, and checksum record.Evidence Summary
gitlink-cli 0.2.0, userZorIgn, targetGitlink/gitlink-cli, score53/100, 10 recorded command events.Gitlink/gitlink-clilocal checkout demo:77/100.96/100.6 passed.9 passed, 0 skipped.skills/, no runtime caches, no local clone directories.Quick Verification
Expected result:
Key Evidence Files
examples/workflows/research-reproducibility-assistant/examples/real_gitlink_outputs/examples/workflows/research-reproducibility-assistant/examples/demo_outputs/examples/workflows/research-reproducibility-assistant/examples/high_evidence_outputs/evidence/track3-rebuild-review-2026-06-30.mdsubmission/competition-entry.mdsubmission/final-submission-index.mdRemote Write Policy
The workflow performs read-only collection by default. Remote Issue creation is outside the automated audit path and requires an explicit operator command after reviewing the generated local Issue draft.