You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Rename project-presence skill to polish-repo
Rename skill, all 5 commands, docs, and cross-references for a shorter,
more memorable name.
* Fix missed rename references per Gemini review
Update headings in naming and identity commands, fix broken
/polish-repo command reference to /polish-repo-audit, and
update AGENTS.md suggestion heading.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
10
10
## [0.24.0] - 2026-03-06
11
11
12
12
### Added
13
-
-**project-presence skill** - New skill for improving open source project discoverability and presentation without relying on social media. Includes 5 phase commands covering README authoring (scratch/improve/replace), naming workshops, visual identity briefs, community infrastructure, and a 100-point audit scoring rubric. Based on analysis of 50+ open source projects across Python, Go, JS, and Rust ecosystems.
13
+
-**polish-repo skill** - New skill for improving open source project discoverability and presentation without relying on social media. Includes 5 phase commands covering README authoring (scratch/improve/replace), naming workshops, visual identity briefs, community infrastructure, and a 100-point audit scoring rubric. Based on analysis of 50+ open source projects across Python, Go, JS, and Rust ecosystems.
14
14
-**Community infrastructure** - Issue templates (bug report + feature request) using GitHub YAML form format, lightweight PR template, CONTRIBUTING.md with dev setup and skill authoring guide, SECURITY.md with spellbook-specific vulnerability scope, and a welcome bot GitHub Action for first-time contributors.
@@ -317,11 +317,11 @@ Reusable workflows for structured development:
317
317
|[/mode]| Switch session mode (fun/tarot/off) |
318
318
|[/pr-distill]| Analyze PR, categorize changes by review necessity |
319
319
|[/pr-distill-bless]| Save discovered pattern for future distillations |
320
-
|[/project-presence-audit]| Phases 0-1 of project-presence: Reconnaissance gathering and audit scorecard generation |
321
-
|[/project-presence-community]| Phase 3 of project-presence: Community infrastructure, issue templates, roadmap, contributor experience, and signs of life |
322
-
|[/project-presence-identity]| Phase 3 of project-presence: Visual identity, badges, GitHub metadata, topics, and documentation strategy |
323
-
|[/project-presence-naming]| Phase 3 of project-presence: Naming workshop, tagline crafting, and positioning strategy |
324
-
|[/project-presence-readme]| Phase 3 of project-presence: README authoring from scratch, improvement, or replacement |
320
+
|[/polish-repo-audit]| Phases 0-1 of polish-repo: Reconnaissance gathering and audit scorecard generation |
321
+
|[/polish-repo-community]| Phase 3 of polish-repo: Community infrastructure, issue templates, roadmap, contributor experience, and signs of life |
322
+
|[/polish-repo-identity]| Phase 3 of polish-repo: Visual identity, badges, GitHub metadata, topics, and documentation strategy |
323
+
|[/polish-repo-naming]| Phase 3 of polish-repo: Naming workshop, tagline crafting, and positioning strategy |
324
+
|[/polish-repo-readme]| Phase 3 of polish-repo: README authoring from scratch, improvement, or replacement |
325
325
|[/advanced-code-review-plan]| Phase 1: Strategic planning for code review |
326
326
|[/advanced-code-review-context]| Phase 2: Context analysis and previous review loading |
327
327
|[/advanced-code-review-review]| Phase 3: Deep multi-pass code review |
@@ -411,11 +411,11 @@ Reusable workflows for structured development:
|[/project-presence-naming](project-presence-naming.md)| Phase 3 of project-presence: Naming workshop, tagline crafting, and positioning ... | spellbook |
72
-
|[/project-presence-readme](project-presence-readme.md)| Phase 3 of project-presence: README authoring from scratch, improvement, or repl... | spellbook |
73
73
|[/reflexion-analyze](reflexion-analyze.md)| Steps 1-3 of reflexion: Parse feedback, categorize root causes, store reflection... | spellbook |
0 commit comments