Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Write and review developer documentation in Google Developer Documentation Style.
Install Google Devdocs Style
$ npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EpicenterHQ/epicenter google-devdocs-style --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/google-devdocs-style .claude/skills/google-devdocs-style && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "google-devdocs-style" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-style into .claude/skills/google-devdocs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-devdocs-style", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-styleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EpicenterHQ/epicenter google-devdocs-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/google-devdocs-style .agents/skills/google-devdocs-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-devdocs-style" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-style into .agents/skills/google-devdocs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-devdocs-style", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EpicenterHQ/epicenter google-devdocs-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/google-devdocs-style .cursor/skills/google-devdocs-style && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-devdocs-style" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-style into .cursor/skills/google-devdocs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-devdocs-style", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EpicenterHQ/epicenter.git --path .agents/skills/google-devdocs-style--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EpicenterHQ/epicenter google-devdocs-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/google-devdocs-style .gemini/skills/google-devdocs-style && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "google-devdocs-style" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-style into .gemini/skills/google-devdocs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-devdocs-style", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EpicenterHQ/epicenter google-devdocs-styleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/google-devdocs-style .github/skills/google-devdocs-style && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "google-devdocs-style" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-style into .github/skills/google-devdocs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-devdocs-style", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EpicenterHQ/epicenter google-devdocs-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EpicenterHQ/epicenter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/google-devdocs-style .opencode/skills/google-devdocs-style && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-devdocs-style" agent skill from https://github.com/EpicenterHQ/epicenter/tree/main/.agents/skills/google-devdocs-style into .opencode/skills/google-devdocs-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-devdocs-style", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
google-devdocs-style- GitHub stars
- 4.8k
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,651 words
- Files
- 4 (incl. references)
- Skills in repo
- 64
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write and review developer documentation in Google Developer Documentation Style.
- Works in 5 steps: The user's explicit request and the… → Source facts: quotations, code,… → Project style. In this repo, AGENTS.md… → …
- Drafting guides
- SKILL.md covers Precedence, Fidelity comes first, The rules that carry the most… and Draft or revise, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Google Devdocs Style is an agent skill from EpicenterHQ/epicenter. Write and review developer documentation in Google Developer Documentation Style. Use when drafting guides, API reference, READMEs, procedures, or release notes, not UI strings, commit messages, PR bodies, or code comments.
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/official-pages.md`, `references/rules.md` and `references/word-list.md`).
It sits in Development, covering Technical documentation, Pull requests and Commit messages. The repository describes itself as: Open-source, local-first apps.
When your agent uses it
- Drafting guides
- Commit messages
Example prompts
- “/google-devdocs-style”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The user's explicit request and the destination's requirements.
- Source facts: quotations, code, commands, filenames, API names, UI labels, product names, and version numbers stay exact even when a style…
- Project style. In this repo, AGENTS.md wins. It bans em dash (U+2014) and en dash (U+2013) characters, so use a colon, comma, semicolon…
- The rules in this file.
- references/ and then the live guide.
What it can do on your machine
Read from SKILL.md and the folder at commit f9441c8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Google Devdocs Style loads about 2.8k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 1,651 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,651 words (~2,757 tokens).
“Produce documentation a developer can act on without rereading: the reader knows who does what, in what order, and what happens next. This skill applies the Google Developer Documentation Style Guide (developers.google.com/style). It is prescriptive by design. Recommend one path…”
- name
- google-devdocs-style
- user-invokable
- true
Files
SKILL.md and 3 other files (references) in .agents/skills/google-devdocs-style of EpicenterHQ/epicenter.
- SKILL.md
- references/official-pages.md
- references/rules.md
- references/word-list.md
Open the folder on GitHubat commit f9441c8
Compare with similar skills
Google Devdocs Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Devdocs Style this skillEpicenterHQ/epicenter | 4.8k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Commit And PR Messagessuperplanehq/superplane | 7.7k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Plane Release Notes Generatormakeplane/plane | 60k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.2k | Automated safety check: Notes | Custom licence |
Similar skills
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Commit And PR Messages
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
More from EpicenterHQ/epicenter
All 64 skills in this repoAgent Instructions
EpicenterHQ/epicenter
Write and maintain repository guidance across AGENTS.md, CLAUDE.md, and .agents/skills.
Consult Claude
EpicenterHQ/epicenter
Get Claude Code's second opinion on a proposal or implementation.
Better Auth Security Best Practices
EpicenterHQ/epicenter
Better Auth security hardening: rate limits, secrets, CSRF, trusted origins, cookies, sessions, OAuth tokens, and audit logging.
Cohesion Over Testability
EpicenterHQ/epicenter
Collapse test-shaped production boundaries while preserving behavior and coverage.
Collapse Pass
EpicenterHQ/epicenter
Remove indirection that does not earn its boundary across a diff or package.
Error Handling
EpicenterHQ/epicenter
Apply Wellcrafted Result patterns to fallible operations and preserve failures at boundaries.
Related
Categories
Questions about Google Devdocs Style
What does Google Devdocs Style do?
Write and review developer documentation in Google Developer Documentation Style. Google Devdocs Style is an agent skill from EpicenterHQ/epicenter. Write and review developer documentation in Google Developer Documentation Style.
When should I use Google Devdocs Style?
Google Devdocs Style fits situations like: drafting guides; commit messages.
How do I install Google Devdocs Style in Claude Code?
Run `npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a claude-code`. Or copy the skill folder (.agents/skills/google-devdocs-style in EpicenterHQ/epicenter) into .claude/skills/google-devdocs-style in your project. Claude Code loads it when a task matches its description.
How do I install Google Devdocs Style in Codex?
Run `npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a codex`. Or copy the skill folder (.agents/skills/google-devdocs-style in EpicenterHQ/epicenter) into .agents/skills/google-devdocs-style in your project. Codex loads it when a task matches its description.
Can I use Google Devdocs Style in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EpicenterHQ/epicenter --skill google-devdocs-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-devdocs-style, .gemini/skills/google-devdocs-style, .github/skills/google-devdocs-style and .opencode/skills/google-devdocs-style in your project.
What does Google Devdocs Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Google Devdocs Style is instructions for the agent only.
Does Google Devdocs Style access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Google Devdocs Style safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Google Devdocs Style use?
Google Devdocs Style has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Google Devdocs Style use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.2k tokens, read only when the agent opens those files.
What are the alternatives to Google Devdocs Style?
Skills that share tags, products or a category with Google Devdocs Style: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Commit And PR Messages (superplanehq/superplane, 7.7k stars) and Plane Release Notes Generator (makeplane/plane, 60k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Devdocs Style?
EpicenterHQ (a GitHub organization) maintains it in EpicenterHQ/epicenter, which has 4,818 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 7, 2026.
Source: EpicenterHQ/epicenter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.