client-report-from-commits skillA
client-report-from-commits is agent-read markdown (skill) from jpcaparas/skills: Turn git commits and diffs since an exact date into a copy-pastable, non-technical client report grouped by feature. Use for client updates, weekly progress, stakeholder recaps, or high-level git-history summaries. Do NOT use when the date is ambiguous..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# client-report-from-commits Turn git history since an explicit date into a copy-pastable, non-technical client update grouped by feature. ## Decision Tree What do you know already? - Exact start date in `YYYY-MM-DD` and the current working directory is the target git repo: continue. - Exact start date in `YYYY-MM-DD`, but the target repo is elsewhere: use the explicit repo path and continue. - Relative or vague date such as "this week", "recently", "a few days ago", or "since the last push": stop and ask `What exact start date should I use? Please reply in YYYY-MM-DD.` Do not proceed until the user answers with an exact date. - No readable git repo in the current working directory and no repo path was provided: stop and ask for a readable git repository path. - The user wants engineering release notes, a developer changelog, or a code review: do not use this skill. ## Quick Reference | Task | Action | | --- | --- | | Confirm the repo | Run `git rev-parse --show-toplevel` in the current directory, or `git -C /path/to/repo rev-parse --show-toplevel` when a repo path is provided. | …
Read the whole file at its exact version.
How to install
mdr add jpcaparas/skills/client-report-from-commits@git:20260912.938fe03mdr add jpcaparas/skills/client-report-from-commits@sha256:a2814380e32984c7Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_g4f665pv2jzq2kd4)
1 badge views in 30 days
Versions
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 (4837 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
jpcaparas/skills · 51 stars · license none · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g4f665pv2jzq2kd4 GET https://markdownregistry.com/api/v1/resolve?ref=jpcaparas/skills/client-report-from-commits GET https://markdownregistry.com/api/v1/blob/a2814380e32984c71b8a9255871b991a8a90223e11d737584225a0d52d199e5c
Your agent 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.