Repository navigation
#44: remove living doc layer - #45
Open
miroslavpojer wants to merge 6 commits into
Open
miroslavpojer wants to merge 6 commits into
miroslavpojer wants to merge 6 commits into
Conversation
…o AbsaOSS/living-doc
…o AbsaOSS/living-doc
miroslavpojer
marked this pull request as ready for review
October 12, 2026 10:17
miroslavpojer
requested review from
lsulak,
oto-macenauer-absa and
tmikula-dev
as code owners
October 12, 2026 10:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Deletes the living-doc part of this repository. It now lives in
AbsaOSS/living-docunderagentic/, next tothe canon it writes, and ships from there:
AbsaOSS/living-doc#53.Complete removal — no pointer, no redirect, no stub folder. Anyone looking for these skills finds them in
living-doc'sREADME.mdand in itsagentic/README.md.Why now: two copies of the same skills existed, and this one reads canon references pinned to a
living-doccommit that has since moved on, so its copies are stale and would drift further with every canon change. A user
installing from here would get skills that disagree with the canon.
#40was closed rather than merged, somasternever received the canon alignment — what is here is the older state, with nothing to preserve.Key Changes
(
data-cy-instrument,gherkin-step,bdd-maintain), all ofskills/shared/, theliving-doc-bdd-copilotagent with its evals, the 13 guides for them, and.github/workflows/test-scripts.yml.getting-started walkthrough, and the two agent guides.
Why
skills/shared/goes wholeOn
masterit held nothing but living-doc material:SKILL.md,lib/(ac_tag.py,living_doc_id.pyandtheir two tests) and
references/(two canon copies plus three JSON schemas). Nothing outside the deletedskills referenced
shared/liborshared/references—git grep -l -e shared/lib -e shared/references -- skills/over the skills that stay returns nothing.There was no canon sync script on
master:scripts/sync-living-doc-reference.shonly ever existed on theclosed
#40branch, so the two canon copies here were hand-maintained and stale. They go withshared/.Why the test workflow goes
test-scripts.ymlhas one job: it discoversskills/**/test_*.pyand runs each file. After this deletion notest_*.pyfile remains anywhere underskills/, so the job would pass on an empty set and report green. Aworkflow that tests nothing is worse than no workflow.
check-pr-requirements.ymlis now the only workflow, andit references no path under
skills/.What changed on the six pages
README.mdliving-doc-bdd-copilotwas the only agent, so the section would have been a heading over an empty table. The FAQ entry explaining skills versus agents stays.docs/README.mdCONTRIBUTING.mdREADME.mdrecording consumers — is now stated directly instead of by reference.docs/getting-started.mddocs/guides/agent-design.mddocs/testing/agent-testing.mddescription:examples use a release agent.agent-design.mdandagent-testing.mdteach how to write any.agent.mdand only illustrated the pointwith the living-doc agent, so the guidance stays and the examples changed.
.github/agents/is now empty, whichmatches the README's own scope statement: agents are something this repository may host, not something it ships
today.
Verification
No relative link in any Markdown file is broken, and no workflow references a deleted path.
One check for the reviewer: three skills are missing from the
README.mdcatalog —create-issue,create-repository-workspaceandpython-standards. All three were already missing before thischange; this PR adds no fourth. The
create-repositoryrow was briefly lost while editing and has been restoredfrom
masterverbatim.Related
Closes #44