Docs Ci logo

Docs Ci

Community
jh941213
docs-ci

Scaffold a docs-as-code CI/CD pipeline + docs drift detection — link check, OpenAPI lint/breaking gate, mermaid validation, docs freshness check, CHANGELOG automation, docs.yaml manifest. Use when installing docs CI/pipelines, detecting docs drift/freshness, docs sync automation, link checks, changelog automation. Writing doc content → docs-architecture/interfaces/manuals; not for the app's own deploy pipeline

Overview

Publisherjh941213
Repositorymy-cc-harness
Skill namedocs-ci
Stars
125
Forks
35
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by jh941213 on GitHub. Read the source before you install it.

Installation

Install the Docs Ci AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/jh941213/my-cc-harness.git /tmp/my-cc-harness
mkdir -p .claude/skills
cp -r /tmp/my-cc-harness/skills_en/docs-ci .claude/skills/docs-ci
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Docs Ci in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Docs Ci on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Docs Ci is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Docs CI Skill — validate docs like code

Builds the pipeline that guards the docs, not the docs themselves. Output: GitHub Actions workflow + drift detection script + the docs/docs.yaml manifest convention.

Input

$ARGUMENTS

The docs.yaml manifest (the drift-detection contract)

Written by every skill in the docs suite; consumed by this skill's checks:

yaml
# docs/docs.yaml — doc ↔ code mapping
docs:
  - path: docs/ARCHITECTURE.md
    covers: ["src/**"]          # code paths this doc describes
    last_reviewed: 2026-07-27   # last human/agent review date
  - path: docs/api/openapi.yaml
    covers: ["src/api/**", "src/routes/**"]
    last_reviewed: 2026-07-27
  - path: docs/ops/runbooks/
    covers: ["deploy/**", "monitoring/**"]
    last_reviewed: 2026-07-27
review_max_age_days: 90

Stale verdict: the latest commit under covers is newer than last_reviewed, or the review age exceeds review_max_age_days.

Checks it installs (pick per project)

CheckTool/methodFailure policy
Broken linkslychee (lycheeverse/lychee-action)internal broken = fail, external = warn
OpenAPI styleredocly lint or spectral lintfail
API breaking changesoasdiff breaking base rev --fail-on ERRfail + PR comment
Code-first spec driftregenerate spec in CI → git diff --exit-codefail
Mermaid syntaxextract blocks → mmdc -i x.mmd -o /dev/nullfail
Docs freshnessscripts/check-docs-freshness.sh (docs.yaml-based)warn (or open an issue)
Code+doc co-changesrc/api/** changed && docs/api/** untouched → PR warning commentwarn
CHANGELOGconventional commits + git cliff (on release)auto-generated
Preview deploysper-PR preview URL if a docs site exists

CHANGELOG automation note: if commits use the [type] title format (rules/git-workflow.md), that is not conventional commits, so git-cliff needs a custom parser (commit_parsers) configuration.

Procedure

  1. Diagnose the project: which docs/specs exist (docs/, openapi.*, mermaid blocks, docs site generator)
  2. Install only checks that match what exists — no spectral gate for a project without OpenAPI
  3. Create/update docs/docs.yaml (scan existing docs to draft covers — include comments so users can refine)
  4. Create {project}/scripts/check-docs-freshness.sh — copy the template templates/check-docs-freshness.sh into the target project's {project}/scripts/
  5. Create .github/workflows/docs-ci.yml (only the needed jobs from templates/docs-ci.yml) — the trigger branch is fixed to main, so adjust to the branching strategy (add develop if it is in use)
  6. Run once locally and report: bash scripts/check-docs-freshness.sh

Harness integration (with this plugin's other components)

  • TTH mode: hooks/docs-sync.sh queues changed files into .docs-queue/ per completed story → ralph-loop spawns docs-writer. docs-ci is the final layer that re-verifies in CI
  • /docs sync command: report stale docs from docs.yaml → delegate updates to the matching docs-* skill

Constraints

  • Create only workflows/scripts/docs/. Never modify app source
  • Checks requiring uninstalled tools: continue-on-error or conditional (if: hashFiles(...))
  • If a CI workflow already exists, add a separate docs-ci.yml — never overwrite

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Docs Ci AI skill do?

Scaffold a docs-as-code CI/CD pipeline + docs drift detection — link check, OpenAPI lint/breaking gate, mermaid validation, docs freshness check, CHANGELOG automation, docs.yaml manifest. Use when installing docs CI/pipelines, detecting docs drift/freshness, docs sync automation, link checks, changelog automation. Writing doc content → docs-architecture/interfaces/manuals; not for the app's own deploy pipeline

Why use Docs Ci on TypingMind?

Because you install it once and use it with any model. Docs Ci is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Docs Ci in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jh941213/my-cc-harness/tree/main/skills_en/docs-ci. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Docs Ci?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Docs Ci?

As many as you like. As long as a model supports skills, you can use Docs Ci with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Docs Ci AI skill free?

It is published on GitHub by jh941213. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇