Packs

2 packs

Results for “technical-blog”

9 skills
More results
getsentry
blog-writing-guide
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar.
845
zero-yx
tech-impl-deep-dive-writer
Writes mechanism-first technical implementation deep-dive articles that explain design intent, data flow, trade-offs, and operations, with code locations as supporting evidence.
0 · bundle
kvn8888
retrospective
Creates a technical journey retrospective document from a coding session, capturing decisions, tradeoffs, and debugging moments in a developer blog post style.
3 · bundle
github
brag-sheet
Turn engineering work into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates by mining Copilot CLI session logs, git history, and GitHub PRs.
36.2k
jarbitechture
tech-debt
Scan, prioritize, and report technical debt. Usage: /tech-debt <scan|prioritize|report> [options]
0
nexu-io
deck-tech-sharing
Creates a tech sharing deck for internal engineering talks with GitHub-dark theme and JetBrains Mono code blocks.
· bundle
kk20300113-png
qa
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".
0