update-feature-docs SKILL.md skillA
update-feature-docs from lukaskellerstein/claude-my-marketplace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lukaskellerstein/claude-my-marketplace/update-feature-docs@git:20260912.4545567Pins git:20260912.4545567 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lukaskellerstein/claude-my-marketplace
- Path
plugins/dev-tools-plugin/skills/update-feature-docs/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260912.4545567, committed Sep 12, 2026
- First version recorded
- Apr 6, 2026
- Size
- 6,613 bytes
- Repository stars
- 3
- License
- none declared
Generate or update documentation for the current feature branch. Analyzes all changes (commits, diffs) between the feature branch and base branch, then creates or updates docs/features/<index>_<feature-name>/README.md with incremental indexing based on existing feature docs. Use when documenting a feature branch, creating feature documentation from branch changes, or updating existing feature docs after additional commits. <example> Context: User wants to document their feature branch user…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Update Feature Documentation
Generate or update documentation for the current feature branch by analyzing all changes since it diverged from the base branch.
## Prerequisites
- Must be on a feature branch (not `main` or `master`). If on main/master, inform the user and stop.
- The `docs/features/` directory should exist. If it doesn't, create it with a `README.md` index.
## Workflow
### Step 1: Detect Branch and Gather Changes
```bash
CURRENT_BRANCH=$(git branch --show-current)
BASE_BRANCH="${1:-main}" # Accept base branch as argument, default to main
```
If on `main` or `master`, tell the user to switch to a feature branch and stop.
Gather all changes:
```bash
# All commits on this branch
git log ${BASE_BRANCH}..HEAD --oneline
# All files changed
git diff ${BASE_BRANCH}...HEAD --name-only
# Diff stats
git diff ${BASE_BRANCH}...HEAD --stat
# Full diff for understanding changes
git diff ${BASE_BRANCH}...HEAD
```
Read ALL changed files to understand the full scope of the feature.
### Step 2: Determine Feature Name
Derive the feature name from the branch name:
- `feature/user-notifications` -> `user-notifications`
- `feat/add-payment-gateway` -> `add-payment-gateway`
…Read the whole file at its exact version.
How to install
mdr add lukaskellerstein/claude-my-marketplace/update-feature-docs@sha256:1681d36795edfc85The line at the top of this page pins the label git:20260912.4545567, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kxojiffgcp42aja7)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 6, 2026 and Sep 12, 2026, about one every 80 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260912.4545567 latest | 2026-09-12 | 4545567 | 6,613 B | A | view · diff |
| git:20260802.00b0d3d | 2026-08-02 | 00b0d3d | 6,575 B | A | view · diff |
| git:20260406.f86f8b0 | 2026-04-06 | f86f8b0 | 6,544 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6613 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lukaskellerstein/claude-my-marketplace · 3 stars · license none declared · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kxojiffgcp42aja7 GET https://markdownregistry.com/api/v1/resolve?ref=lukaskellerstein/claude-my-marketplace/update-feature-docs GET https://markdownregistry.com/api/v1/blob/1681d36795edfc85c047bb404b89d7845111f3d8de0cfe51501a87c593499824
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.