mirror of https://github.com/Dimillian/Skills.git synced 2026-03-25 08:55:54 +00:00

feat: improve 8 skills with targeted optimizations

Hullo @dimillian 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| swiftui-ui-patterns | 81% | 100% | +19% |
| github | 85% | 100% | +15% |
| macos-spm-app-packaging | 86% | 100% | +14% |
| react-component-performance | 86% | 100% | +14% |
| swift-concurrency-expert | 88% | 100% | +12% |
| app-store-changelog | 93% | 100% | +7% |
| ios-debugger-agent | 94% | 100% | +6% |
| swiftui-view-refactor | 93% | 95% | +2% |
| swiftui-liquid-glass | 100% | 100% | — |
| swiftui-performance-audit | 100% | 100% | — |

<details>
<summary>Changes made</summary>

**swiftui-ui-patterns** — Expanded description with additional trigger terms (VStack/HStack, @State, @Binding, navigation hierarchies, custom view modifiers). Added explicit build validation checkpoints and error recovery guidance to the workflow steps.

**github** — Added explicit "Use when..." clause with natural trigger terms (check CI status, create PR, list issues). Added a structured "Debugging a CI Failure" numbered workflow organizing existing commands into a clear investigation sequence.

**macos-spm-app-packaging** — Added a minimum end-to-end example (bootstrap to running app). Added validation checkpoints after packaging, signing, and notarization with specific verification commands (codesign, spctl, stapler). Added a common notarization failures troubleshooting table.

**react-component-performance** — Added three concrete before/after code examples (isolate ticking state, stabilize callbacks with useCallback + memo, derived data with useMemo). Expanded profiling validation with explicit React DevTools Profiler steps.

**swift-concurrency-expert** — Expanded description with concrete actions (adding Sendable conformance, @MainActor annotations, resolving actor isolation warnings). Added verification step to workflow. Added three before/after Swift code examples covering @MainActor, protocol conformance isolation, and @concurrent.

**app-store-changelog** — Added commit-to-bullet transformation examples showing how raw commits map to user-facing App Store bullets, plus examples of internal-only commits that get dropped. Added a complete example "What's New" output block.

**ios-debugger-agent** — Added build failure handling and post-launch verification checkpoints to the core workflow (verify app launched via describe_ui or screenshot before proceeding to UI interaction).

**swiftui-view-refactor** — Tightened prose in sections 3, 3b, and large-view handling. Removed a redundant example. Converted workflow list to clean numbered format.

</details>

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

If you want to run reviews, evals and optimizations yourself, just `npm install @tessl/cli` then run `tessl skill review path/to/your/SKILL.md`, and click here (https://tessl.io/registry/skills/submit) to find out more.

Thanks in advance 🙏

2026-03-06 16:53:32 +00:00

2.9 KiB

Raw Blame History

name	description
app-store-changelog	Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.

App Store Changelog

Overview

Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.

Workflow

1) Collect changes

Run scripts/collect_release_changes.sh from the repo root to gather commits and touched files.
If needed, pass a specific tag or ref: scripts/collect_release_changes.sh v1.2.3 HEAD.
If no tags exist, the script falls back to full history.

2) Triage for user impact

Scan commits and files to identify user-visible changes.
Group changes by theme (New, Improved, Fixed) and deduplicate overlaps.
Drop internal-only work (build scripts, refactors, dependency bumps, CI).

3) Draft App Store notes

Write short, benefit-focused bullets for each user-facing change.
Use clear verbs and plain language; avoid internal jargon.
Prefer 5 to 10 bullets unless the user requests a different length.

4) Validate

Ensure every bullet maps back to a real change in the range.
Check for duplicates and overly technical wording.
Ask for clarification if any change is ambiguous or possibly internal-only.

Commit-to-Bullet Examples

The following shows how raw commits are translated into App Store bullets:

Raw commit message	App Store bullet
`fix(auth): resolve token refresh race condition on iOS 17`	• Fixed a login issue that could leave some users unexpectedly signed out.
`feat(search): add voice input to search bar`	• Search your library hands-free with the new voice input option.
`perf(timeline): lazy-load images to reduce scroll jank`	• Scrolling through your timeline is now smoother and faster.

Internal-only commits that are dropped (no user impact):

chore: upgrade fastlane to 2.219
refactor(network): extract URLSession wrapper into module
ci: add nightly build job

Example Output

What's New in Version 3.4

• Search your library hands-free with the new voice input option.
• Scrolling through your timeline is now smoother and faster.
• Fixed a login issue that could leave some users unexpectedly signed out.
• Added dark-mode support to the settings screen.
• Improved load times when opening large photo albums.

Output Format

Title (optional): "What's New" or product name + version.
Bullet list only; one sentence per bullet.
Stick to storefront limits if the user provides one.

Resources

scripts/collect_release_changes.sh: Collect commits and touched files since last tag.
references/release-notes-guidelines.md: Language, filtering, and QA rules for App Store notes.

2.9 KiB Raw Blame History