UnigramDev/Unigram/develop • a7d3657 • 1 files, +8/-4
Improve quote style

UnigramDev/Unigram/develop • e068bd3 • 1 files, +22/-5
crash-triage: correct the PR base and branch naming

Two things went wrong on the first real run of this skill.

The PR must be based on GitHub's develop, not on origin/develop inside a
clone of the user's repo. That ref is their remote-tracking branch: it was
both stale and carrying unpushed local commits, so it had diverged from the
branch the PR actually merges into, and the file being patched differed
between the two. Add the GitHub remote explicitly and branch from there.

Branches cannot be prefixed with fix/, because a branch literally named "fix"
exists on the remote and git rejects the push with "directory file conflict".

Also requires stating whether the change was built and run. A UWP/.NET Native
build is usually unavailable here, and a reviewer should not have to guess.
Roslyn parsing is offered as the weaker check it is, with its limits spelled
out.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

UnigramDev/Unigram/develop • 79e90af • 1 files, +20/-7
crash-triage: never publish crash impact numbers

The repository is public, so affected-user counts, device counts and per-OS
breakdowns are private telemetry being published to the world. The PR
template asked for exactly that, and the first real run put "46 crashes / 32
users" into both a PR body and a pushed commit message.

Impact figures are now explicitly for choosing what to work on, never for
justifying it in public. PRs say "reported by crash telemetry on <version>"
and nothing more; group hashes and device breakdowns stay out too.

Calls out that the commit message is as public as the PR body and must be
checked before pushing, since scrubbing it afterwards needs a force-push.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

UnigramDev/Unigram/develop • 6a24748 • 1 files, +12/-3
crash-triage: generate public text with crashctl --public

Stripping impact figures by hand already failed once, so point the skill at
the mechanical path instead: crashctl show --public emits the exception, the
frames and the missing-symbol list with impact figures, device/OS breakdown,
group hash and log tail withheld.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

#unigram