SkillAgentSearch skills...

commit-docs

Word add-in that checks for consistency across the document and can set a style by training on a style sample

Install / Use

npx skills add Gekko47/ToneForge

Installs into whichever agent you are using.

About this skill
🔧

.clinerules

Cline rules

Quality Score

59/100

Supported Platforms

Cline

Tags

Our assessment of commit-docs

commit-docs scores 59/100 on our quality scale, 1108th of 1,148 Content & Media skills we index.

Its .clinerules is 2.8 KB long, well organised into 8 sections with 1 code example: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
17/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

commit-docs compared with similar skills

All 4 of these similar skills score higher than commit-docs; compare them before choosing.

SkillScoreStarsUpdatedFormat
commit-docs (this skill)by Gekko47590—.clinerules
siyuanby siyuan-note10047.3ktodayMCP Server
ad-creativeby coreyhaines3110060.1k11d agoSKILL.md
imageby coreyhaines3110060.1k11d agoSKILL.md
changelog-videoby heygen-com10083.8k9d agoSKILL.md

Frequently asked questions

How do I install commit-docs?
Run npx skills add Gekko47/ToneForge. The install tabs above show the steps for each supported agent.
Which AI agents does commit-docs work with?
It is written for Cline, as a .clinerules file. Other agents that read the same format can often use it too.
Is commit-docs safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is commit-docs still maintained?
We could not determine when the repository was last updated.

paths:

  • "ROADMAP.md"
  • "docs/decision-log.md"
  • "docs/project-state.md"
  • "docs/stages/**"
  • "docs/CHANGELOG.md"
  • "commitlint.config.cjs"
  • ".husky/**"

Commits and Documentation

Rules

1. Conventional commits with roadmap-aligned scopes

Type must be one of build, chore, ci, docs, feat, fix, perf, refactor, revert, spike, style, test, security. Scope matches the stage or phase:

feat(word): add native revision adapter              # Stage 18
feat(style): add deterministic style metrics         # Stage 09
feat(ai): add resilient provider adapters             # Stage 06
spike: verify Word revision and document capabilities # Stage 01
chore: scaffold ToneForge Office add-in              # Stage 02
test: complete regression and review pass            # Stage 26

The body explains the why, and references the stage file and any ADR.

2. Update the status where it actually lives

ROADMAP.md is the canonical roadmap, status ledger, and release-gate record. docs/project-state.md is a compatibility and evidence index that cross-references it, not a second plan. When they disagree, ROADMAP wins. Do not duplicate a status table in project-state.

State a stage as PASS, PASS WITH DOCUMENTED LIMITATION, IMPLEMENTED, PARTIAL, BLOCKED, or NOT STARTED, and say which gates were checked and what remains open.

3. Record architectural decisions as ADRs

Any new module boundary, schema change, dependency, or API contract gets an ADR in docs/decision-log.md with Context, Decision, Consequences, and Status. Update an existing ADR when a decision is revisited — do not append a contradictory entry. Take the next ADR number; do not reuse one.

Record an exception as an exception. ADR-0052 authorizes one non-deterministic engine. A second one contradicts it and needs its own ADR saying so.

4. Never claim verification you did not perform

A mocked host is a typed contract, not an integration. A green automated graph is not a release. When something has never run against a real document, a real model, or a real Word host, say so in the status — a limitation written down is fine, a limitation reported as working is not.

5. Never commit secrets

Keys live only in the gitignored .env (read by the Node-side development broker) or in the local gateway's memory. .env.example is the committable template. npm run secrets:scan and secrets:verify-build run in the graph.

Referenced resources

Related Skills

View on GitHub
GitHub Stars0
CategoryContent
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low