dev-workflow

What it does and when to use it

Standardized Github operations, Diátaxis documentation framework, and visual assets. Use when: git workflow, github, gh cli, documentation, diataxis, restructure docs.

How it works

1. Goal
2. Steps
3. Security & Guardrails

---
name: dev-workflow
description: "Standardized Github operations, Diátaxis documentation framework, and visual assets. Use when: git workflow, github, gh cli, documentation, diataxis, restructure docs."
license: CC-BY-SA-4.0
metadata:
  source: "agents/skills/ops/dev-workflow.skill.md"
  tags: "git, github, documentation, diataxis"
  core: "false"
  context_cost: "low"
---
# Developer Workflow & Documentation Organizer

## Goal
You have been invoked to refine project documentation, execute complex git workflows via `gh` CLI, or restructure the codebase's narrative form.

## Steps
1. READ `agents/guides/ops/dev-workflow.md`.
2. Always select (and ask the user to select/confirm) the best guides and skills for the specific task and context before proceeding. Additionally, proactively recommend any not-enabled MCP servers (universal or task-specific) that would optimally assist with the workflow. **CRITICAL**: Default to cost and budget optimizations during these actions unless expensive operations are absolutely required; in which case, you must explicitly ask the user for approval.
3. Analyze the user request. Does it involve code commits? Does it involve documentation?
3. If documenting:
   - Identify which Diátaxis quadrant the requested text belongs to (Tutorial, How-To, Reference, Explanation).
   - Author the documentation keeping strictly to the constraints of that quadrant.
4. If managing git:
   - Use `git status`, `git log`, and `gh pr status` to orient yourself.
   - Use interactive rebase if history needs cleaning.
   - Ensure all commits use Conventional Commits formatting.

## Security & Guardrails
- Never document sensitive environment variables, internal IP routes, or PII in cleartext markdown files.
- Never force push (`git push -f`) to a shared branch without explicit human coordination. Use `--force-with-lease` if absolutely necessary on personal feature branches.
- Follow the overarching rules defined in `AGENTS.md` and `CONSTITUTION.md`.

Versions

Database snapshot: 13.11.2026 · package version 84dc4461cfbc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100docs-writing
  Use when asked to write, restructure, or audit documentation with Diataxis types, or to draft a feature docs page or diagram source. Not for ADRs or architectural rationale.
• 100diataxis
  Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what…
• 100documentation
  Creates, structures, and reviews technical documentation following the Diátaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API…
• 100diataxis-docs
  Generate a complete Diátaxis documentation set (tutorials, how-to guides, reference, explanation) from a codebase. Use ONLY when the user explicitly invokes /diataxis-docs or asks for this skill by name — never for incidental documentation requests like editing a README.
• 85diataxis
  Write or review documentation using the Diátaxis framework. Use when the user asks for a tutorial, how-to guide, technical reference, explanation/conceptual doc, README, a documentation plan, or a review/audit of existing docs. Classifies the request into the right quadrant and…
• 100diataxis
  Author and restructure technical documentation with the Diátaxis framework — tutorials, how-to guides, reference, and explanation. Use when writing or reorganising docs, when a page mixes instruction with description or discussion, when deciding where a piece of content belongs,…