Results for “technical-blog”

Tech Blog Article

Weekly engineering retrospective. (gstack)

Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.

Write product-facing technical specs that clarify decisions, constraints, dependencies, and rollout.

Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

Weekly engineering retrospective. (gstack)

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Blog Writing

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans.

Creates a tech sharing deck for internal engineering talks with GitHub-dark theme and JetBrains Mono code blocks.

Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

Internal technical readiness drill assistant for release and handoff.

Load this skill when the user says "tech debt", "tech-debt", or "/tech-debt", or asks to file/track something they've identified as tech debt. Verifies the claimed problem still exists in the current code, drafts a single [Tech Debt]-prefixed issue from `.github/ISSUE_TEMPLATE/tech-debt-issue.md`, and creates it via `gh issue create` only after the user approves the draft.

Weekly engineering retrospective. (gstack)

Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

Scan codebases for technical debt, score severity, track trends, and generate prioritized remediation plans. Use when users mention tech debt, code quality, refactoring priority, debt scoring, cleanup sprints, or code health assessment. Also use for legacy code modernization planning and maintenance cost estimation.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

This skill should be used when the user asks to "write an article", "help me write a blog post", "draft a technical article", "review my article", "check my writing", "improve this draft", "give me writing feedback", "find a topic", "what should I write about", or mentions "writing coach". Provides comprehensive guidance including topic selection, 17 writing skills, and reviewer collaboration from "Writing for Developers" by Piotr Sarna & Cynthia Dunlop.