Render provenance into local PRD and design artifacts (#117) - #118
Render provenance into local PRD and design artifacts (#117)#118tchughesiv wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (10)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📜 Recent review details🧰 Additional context used📓 Path-based instructions (6)Injection prevention (prodsec-skills): SQL: parameterized queries only; no string concatenation Command: no shell=True, os.system, or backtick exec with user input LDAP/XPath: escape special characters in filters Path traversal: canonicaliz...⚙️ CodeRabbit configuration file Files:
Workflow script review (ai-workflows conventions): Scripts must be invoked by skill files, not by users directly Must work when the workflow is installed via symlink Exit code conventions must be documented in docstring: Report scripts: 0 =...⚙️ CodeRabbit configuration file Files:
Workflow skill review (ai-workflows conventions): First classify the file as a phase implementation, controller, dispatcher, completion guide, or other support file.⚙️ CodeRabbit configuration file Files:
SKILL.md review (ai-workflows conventions): YAML frontmatter required: opening/closing --- delimiters Required fields: name (lowercase, hyphens only, max 64 chars), description (third person, includes trigger terms and activated-by commands...⚙️ CodeRabbit configuration file Files:
Shared resource review (ai-workflows conventions): Shared resources may be referenced by multiple packages — changes here have cross-cutting impact.⚙️ CodeRabbit configuration file Files:
Cross-package consistency (ai-workflows conventions): Package-resource references that an agent follows must be relative for symlink compatibility.⚙️ CodeRabbit configuration file Files:
🪛 ast-grep (0.45.3)_shared/scripts/test_provenance.py[info] 718-733: use jsonify instead of json.dumps for JSON output (use-jsonify) [info] 793-799: use jsonify instead of json.dumps for JSON output (use-jsonify) [info] 812-818: use jsonify instead of json.dumps for JSON output (use-jsonify) 🔇 Additional comments (10)
WalkthroughThe shared provenance recipe now supports local artifacts and docs-repository copies. PRD and design workflows render footers on source artifacts before synchronization. Tests cover ordering, copying, and footer replacement. ChangesProvenance footer workflow
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Feature Merge Risk: ⚪ Minimal · up to PRD and design artifacts now retain updated provenance footers before documentation copies are synchronized. The change is covered for ordering, copy persistence, and footer replacement, with no current merge-blocking risk identified. Suggested labels: Suggested reviewers: Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error, 1 warning)
✅ Passed checks (10 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 5 functions across 1 files. (9 skipped: 9 unsupported.) Full details: Ai-AttributionExplanation The PR context states that CodeRabbit was used for the review. The two PR commits (
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai full review |
✅ Action performedFull review finished. |
Render provenance into local PRD and design artifacts
Issue: #117
Type: GitHub issue
Summary
Render provenance directly into local PRD and design artifacts immediately after
draft, revise, and respond phases capture a provenance event. This makes the
artifact independently readable before any optional documentation-repository
sync while retaining the existing published-copy rendering behavior.
Changes
as documentation-repository files.
respond phase paths, before optional documentation sync.
accumulated-event rerendering.
Testing
python3 -m unittest discover -s _shared/scripts -p 'test_*.py' -vpython3 -m unittest discover -s triage/scripts -p 'test_*.py' -vpython3 -m unittest discover -s skills/report-bug/scripts -p 'test_*.py' -vbash .github/scripts/test-install.shpython3 skill-reviewer/scripts/pre-review-checks.py --all --repo-root .git diff --check origin/main...HEADThe repository version-validation script requires GNU
head; Linux CI is theauthoritative environment for that check. Markdown linting is also CI-only.
Acceptance Criteria
machine-readable provenance marker.
PR.
Summary
_shared/recipes/render-provenance-footer.mdto support local artifacts and documentation-repository copies. Retain published-copy behavior.0.10.0. Add regression tests for local rendering and accumulated provenance events.