repo-article

To generate an evidence-backed article from GitHub repository activity, the Skill gathers recent commits, merged PRs, issues, and external mentions to construct a falsifiable, thesis-driven narrative about the repo's trajectory.

Yes, you can automate thesis-driven repo reporting by pulling GitHub API data and using memory sources like watched-repos.md to shape the narrative across a four-phase research, drafting, self-editing, and publication workflow.

A falsifiable repo article is a publish-ready document that states a specific thesis about a repository's recent trajectory and backs it with verifiable data. You need one when requiring disciplined, reproducible repository analysis.

Yes, you need to set up memory files such as memory/MEMORY.md and memory/watched-repos.md before drafting articles, as these sources shape the narrative and provide the context required for the four-phase workflow.

To force a specific angle when generating a repo article, you must pass a forced angle via the `${var}` variable, which tailors the thesis and ensures the generated narrative aligns with your intended analytical perspective.

The best way to ensure reproducibility in content automation is using a phase-driven workflow with a built-in quality gate that aggregates verifiable evidence from GitHub activity and external mentions to support a falsifiable argument.