Technical Writing

Building, rendering library docs, and deploying docs.cloudposse.com. Use when working with the Docusaurus build process or regenerating auto-generated content.

Writing standards, React components, and MDX patterns for docs.cloudposse.com. Use when creating or editing documentation content.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Ingest new procedural memory (skills, patterns, docs) into the vector database.

Create, review, and refactor project documentation (README, AGENTS.md, architecture docs, runbooks, API docs) with deep codebase analysis, clear markdown structure, and diagrams/user flows. Use when asked to write or improve docs, audit existing documentation for accuracy or quality, generate diagrams/flows, or assess agent-first docs like AGENTS.md/PLANS.md for freshness and completeness.

Systematic approach for gathering authoritative, version-accurate documentation. Claude invokes this skill when research is needed before implementation. Ensures truth over speed while achieving both.

Analyze and enhance Makefiles for complete user functionality coverage. Triggers: Makefile analysis, Makefile gaps, missing targets, plugin release, Makefile coverage, build targets, make dogfood, plugin quality Use when: analyzing Makefile completeness before releasing plugins, identifying gaps during plugin maintenance, scoring Makefiles against best practices, verifying Makefiles support standard developer workflows DO NOT use when: writing initial Makefiles from scratch. DO NOT use when: debugging specific build target failures. DO NOT use when: creating custom non-standard build systems. Use this skill BEFORE releasing any plugin to verify Makefile coverage.

JS/TS conventions for syntax, modules, and types. Use when writing or reviewing JavaScript/TypeScript code.

Generate program dashboards, GitHub-ready comment digests, and CSV summaries sourced from Minister's tracker data. Triggers: initiative pulse, status report, weekly update, stakeholder briefing, github dashboard, blocker radar, initiative health, program metrics Use when: creating status reports, weekly updates, stakeholder briefings, generating GitHub comment digests, tracking initiative health DO NOT use when: release gates/readiness - use release-health-gates. DO NOT use when: project planning - use spec-kit:speckit-orchestrator. Outputs markdown digests and CSV exports for GitHub issues and PRs.

Complete guide for writing Claude Code and SDK hooks with security-first design. Triggers: hook creation, hook writing, PreToolUse, PostToolUse, UserPromptSubmit, tool validation, logging hooks, context injection, workflow automation Use when: creating new hooks for tool validation, logging operations for audit, injecting context before prompts, enforcing project-specific workflows, preventing dangerous operations in production DO NOT use when: logic belongs in core skill - use Skills instead. DO NOT use when: complex multi-step workflows needed - use Agents instead. DO NOT use when: behavior better suited for custom tool. Use this skill BEFORE writing any hook. Check even if unsure.

Consolidates ephemeral LLM-generated markdown files into permanent documentation. Triggers: consolidate docs, untracked reports, ephemeral files, git cleanup, report consolidation, knowledge extraction, REPORT.md files, ANALYSIS.md files Use when: you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews DO NOT use when: files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value. Merges valuable content into permanent documentation, then deletes source files.

detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment

Declarative release readiness checklist that mirrors GitHub checks, deployment issues, and documentation requirements. Triggers: release gates, release readiness, deployment checklist, release review, quality signals, rollout scorecard, QA handshake, deployment gates Use when: preparing releases, validating deployment gates, conducting release reviews, embedding release gate snippets in PRs DO NOT use when: weekly status updates - use github-initiative-pulse. DO NOT use when: code reviews - use pensive review skills. Standardizes release approvals with GitHub-aware checklists.

Update and maintain tests following TDD/BDD principles with detailed quality assurance. Triggers: test updates, test maintenance, test generation, TDD workflow, BDD patterns, test coverage, pytest, test enhancement, quality assurance Use when: updating existing tests, generating new tests for features, enhancing test quality, ensuring detailed coverage, pre-commit validation DO NOT use when: auditing test suites - use pensive:test-review. DO NOT use when: writing production code - focus on implementation first. Run git-workspace-review first to understand which tests need updates.

Generic template patterns and lifecycle stages for knowledge storage, configuration management, and structured documentation. Triggers: storage templates, lifecycle stages, maturity progression, naming conventions, knowledge storage, configuration templates, documentation patterns Use when: organizing knowledge storage, managing configuration lifecycle, creating structured documentation, establishing naming conventions DO NOT use when: simple storage without lifecycle or structure needs. Consult this skill when designing storage and documentation systems.

Methodology for summarizing changes, extracting insights, and identifying follow-up actions. Triggers: catchup, what changed, summarize changes, context acquisition, handoff, progress review, recent changes, git log analysis, sprint summary Use when: resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context DO NOT use when: doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead. Use this skill to quickly understand "what changed and what matters".

Workflow for capturing evidence and citations to create reproducible analyses and audit trails. Triggers: evidence capture, citations, reproducible analysis, audit trail, documentation, evidence logging, findings documentation Use when: conducting any review that needs evidence trails, creating audit documentation, ensuring reproducibility of analyses DO NOT use when: quick informal checks without documentation needs. DO NOT use when: structured output is the focus - use structured-output. Use this skill as foundation for all evidence-based review workflows.

Bump project versions across configs, docs, and changelog using git-workspace-review context. Triggers: version bump, semver, release version, changelog update, version update, package version, release preparation Use when: bumping project versions, updating changelogs, preparing releases, coordinating version changes across files DO NOT use when: just documentation updates - use doc-updates. DO NOT use when: full PR preparation - use pr-prep. Use this skill for version management and release preparation.

Generate phased, dependency-ordered tasks from specs. Identifies parallelization opportunities. Triggers: task planning, dependency ordering, phased breakdown, parallel tasks Use when: converting specifications to implementation tasks DO NOT use when: writing specifications - use spec-writing.

Systematically uncover and fix bugs using language-specific expertise and reproducible evidence. Triggers: bug hunting, defect detection, debugging, fix verification, bug fix, regression check, error investigation, defect documentation Use when: deep bug hunting needed, documenting defects, verifying fixes, systematic debugging required DO NOT use when: test coverage audit - use test-review instead. DO NOT use when: architecture issues - use architecture-review. Use this skill for systematic bug hunting with evidence trails.