chore: add publicity-article skill - #239
Open
gimmyhehe wants to merge 2 commits into
Open
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (2)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. WalkthroughUpdated the ChangesPublicity Article Authoring
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR adds a publicity-article skill and related guidance files; no actionable merge-blocking risk remains beyond normal checks and review. Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.) ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.agents/skills/publicity-article/examples.md:
- Around line 14-72: Update the outer Markdown example fence in the documented
example so it uses a longer fence than the nested TypeScript fence, such as four
backticks, while preserving the inner ```ts block and the example content
unchanged.
In @.agents/skills/publicity-article/SKILL.md:
- Line 102: Update the draft-writing instructions in the publicity article
workflow to preserve an existing publicity-article.md: create it when absent,
merge generated content with existing user edits when present, and require
explicit user confirmation before replacing the entire file. Remove the
unconditional overwrite directive while retaining synchronization of approved
user feedback.
- Around line 19-27: Update the progress checklist block in SKILL.md by either
removing the unnecessary fence so the task items render normally, or labeling
the existing fence as markdown; ensure no unlabeled fenced block remains and
preserve the checklist content.
- Around line 59-60: Update the publication-verification guidance in the
numbered rules to require checking the advertised target package version, using
version-qualified npm metadata and inspecting that version’s exports or package
files; do not rely on unqualified latest results when validating package-level
release claims, and retain the rule against mentioning unverified or unpublished
capabilities.
In @.agents/skills/publicity-article/style-guide.md:
- Around line 28-31: Update the “总览写法” guidance and the corresponding overview
topic examples in examples.md to use one consistent heading convention;
explicitly allow both bold labels and ### headings, or change the example to
match the canonical bold-label format.
- Around line 84-88: Update the release-summary template around “GenUI SDK
v{version}” so the bold theme list supports the workflow-selected number of
themes, including Example A’s four themes. Use a variable-length theme
representation, or consistently constrain the workflow and all examples to a
maximum of three themes.
- Around line 81-88: Clarify the placeholder contract in the publicity article
template: define {version} as the bare semantic version without the leading “v”
so the displayed version and release URL produce a single “v” prefix. Update the
surrounding guidance or template wording consistently, preserving the existing
release-link structure.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 7fdc03f3-ac3d-4d21-9fe0-338ccd7cef86
📒 Files selected for processing (3)
.agents/skills/publicity-article/SKILL.md.agents/skills/publicity-article/examples.md.agents/skills/publicity-article/style-guide.md
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
1 participant
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.
新增发布文章skill
Summary by CodeRabbit