From attune-author
Report which feature templates are stale by comparing source file hashes. Triggers on: stale templates, what's outdated, doc status, check help freshness, what changed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/attune-author:author-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Report which feature templates are stale by comparing the
Report which feature templates are stale by comparing the SHA-256 hash of source files against the hash stored in each template's frontmatter.
.help/ in syncIf no help_dir is provided, default to .help/ in the
current project. Use AskUserQuestion only if the path is
ambiguous (multiple .help/ directories visible).
author_status with help_dir and
project_root.report
field.author-maintain to regenerate all, or
author-generate <feature> for a single feature.The MCP tool returns markdown like:
## Help Status
**12** current, **3** stale
### Stale Features
| Feature | Description | Files Changed |
|---------|-------------|---------------|
| auth | Authentication and authorization | 5 source files |
| cli | Command-line interface | 2 source files |
Render this as-is — no further formatting needed.
npx claudepluginhub smart-ai-memory/attune-docs --plugin attune-authorProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.