Add brag-sheet skill — work impact writer for performance reviews#1428
Add brag-sheet skill — work impact writer for performance reviews#1428vidhartbhatia wants to merge 2 commits intogithub:stagedfrom
Conversation
🔍 Skill Validator Results✅ All checks passed
Summary
Full validator output```text Found 1 skill(s) [brag-sheet] 📊 brag-sheet: 1,330 BPE tokens [chars/4: 1,338] (detailed ✓), 18 sections, 3 code blocks ✅ All checks passed (1 skill(s)) ``` |
There was a problem hiding this comment.
Pull request overview
Adds a new brag-sheet skill to the skills/ catalog, aimed at helping developers produce impact-first accomplishment entries and backfill work history for performance reviews.
Changes:
- Introduces a new
skills/brag-sheet/skill with guidance for writing “impact-first” entries. - Adds backfill workflows leveraging git history, Copilot CLI session-state, and GitHub PR history.
- Documents an optional integration with the external
copilot-brag-sheetextension for automatic tracking.
| --- | ||
| name: brag-sheet | ||
| description: > | ||
| Write impact-first work entries for performance reviews. Backfill from git history, | ||
| Copilot session logs, and PRs. Categories: pr, bugfix, infrastructure, investigation, | ||
| collaboration, tooling, oncall, design, documentation. | ||
| --- |
There was a problem hiding this comment.
This PR adds a new skill but does not include the generated docs/table updates. Per CONTRIBUTING, after adding a skill you should run npm run skill:validate and npm run build and commit the resulting README table updates (e.g., the skills index in docs/README.skills.md).
| | ❌ Vague | ✅ Impact-first | | ||
| |---------|----------------| | ||
| | "Fixed a bug in auth" | "Fixed token refresh race condition → eliminated 401s affecting 12% of API calls → PR #247" | |
There was a problem hiding this comment.
The markdown table under “Transform vague descriptions…” is likely malformed because each row starts with ||, which renders as an empty first column in GitHub-flavored Markdown. Use a single leading | (and keep the same column count) so the table renders as intended.
| | ID | Emoji | Use for | | ||
| |----|-------|---------| | ||
| | `pr` | 🚀 | Merged PRs, shipped features | |
There was a problem hiding this comment.
The “Categories” table also starts each row with ||, which will create an unintended empty first column and misalign the table. Update the table rows to use the standard single leading | format so it renders correctly.
Pull Request Checklist
Description
brag-sheet is a skill that helps developers write impact-first work entries for performance reviews, backfill work history from git commits/PRs/session logs, and prepare for review discussions.
What it does (standalone)
Full automatic tracking
The skill mentions the copilot-brag-sheet extension (Microsoft org, MIT) for users who want automatic session tracking. The skill is fully useful without the extension.
Type of Contribution
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.