skills.rest
joabgonzalez
joabgonzalezCOMMUNITY
Explore all skills by this author →
GitHub

technical-communication

Improve technical writing across documentation, code comments, and communications.

7|Updated Jan 29, 2026
Search Tags:#documentation#style-guide#technical-writing#code-comments#commit-messages#adrs#readmes
One-click install
npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill technical-communication
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: technical-communication
Source: https://github.com/joabgonzalez/ai-agents-skills/tree/main/skills/technical-communication
Command: npx skills add https://github.com/joabgonzalez/ai-agents-skills --skill technical-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear technical writing for documentation and commits, enabling teams to communicate concepts accurately and consistently.

Core Features & Use Cases

  • Provides clear, concise writing guidelines for API docs, READMEs, ADRs, and inline code comments.
  • Offers templates and rules to ensure consistent commit messages, PR descriptions, and architectural decisions.
  • Helps teams translate complex technical ideas into actionable, easy-to-understand content with real-world examples.

Quick Start

Apply consistent technical writing standards across your documentation and code comments by following concise prompts.

Frequently Asked Questions about technical-communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write clear technical documentation for API docs and READMEs?▼

Clear technical documentation requires structured guidance, active voice, and concise formatting. Apply these standards to API docs and READMEs to produce precise, actionable text with consistent examples.

What is the best way to format commit messages and PR descriptions?▼

Formatting commit messages and PR descriptions requires templates and rules for consistency. Apply predefined standards to ensure structured, clear communication across pull requests and version control history.

How do I write effective inline code comments?▼

Effective inline code comments require precise, actionable text. Apply concise writing guidelines to inline notes to clarify complex logic and maintain consistent documentation standards across your software project.

When do I need to write an Architecture Decision Record?▼

You need an Architecture Decision Record (ADR) to document architectural decisions consistently. Use structured templates to translate technical decisions into actionable, easy-to-understand content for your team.

Can I enforce a consistent style guide across all technical writing?▼

You can enforce a consistent style guide by applying structured writing rules across all documentation. This ensures precise, actionable text and consistent formatting standards for API docs, READMEs, and ADRs.

Related Skills

Explore More Content & Communication Skills→
joekhosbayarjoekhosbayar

gds-agent-tech-writer

Generates structured technical documentation with Mermaid diagrams and OpenAPI-style explanations from complex concepts.

Community
Advanced
phuthuycodingphuthuycoding
10

documentation

Generate README, API, and architecture documentation from code scans.

Community
Basic
trevin-jtrevin-j
6

git-basics

Run tests, linters, and static analysis before committing with Conventional Commits.

Community
Intermediate
ghalacticghalactic

google-developer-style-guide-naming-terminology

Enforce Google developer documentation style guide capitalization, abbreviations, spelling, and grammar.

Official
Advanced