narumiruna/writing-work-logs
deprecated/writing-work-logs/SKILL.md
Use only when the user explicitly names writing-work-logs to produce a concise, evidence-based Git work log for a resolved date range; never auto-activate for generic status or summary requests.
$ install --global
skillsauthnpx skillsauth add narumiruna/agent-skills writing-work-logsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 23, 2026, 6:30 AM176.4s2 files scanned
SKILL.md
- name:
- writing-work-logs
- description:
- Use only when the user explicitly names writing-work-logs to produce a concise, evidence-based Git work log for a resolved date range; never auto-activate for generic status or summary requests.
- internal:
- true
Writing Work Logs (Deprecated Reference)
Use only after explicit invocation. Operate on one repository and do not save a file unless requested.
Workflow
- Resolve the date range. Check the local date for relative terms; interpret “last week” as the previous calendar week unless context makes “last seven days” materially plausible. Ask for a range when none is provided.
- Gather commits with hashes, dates, authors, and subjects. Identify the current Git user's name/email when filtering a multi-author history; ask only when ownership remains ambiguous.
- Inspect
git show --stator--name-onlywhen subjects do not support a reliable summary. For a range including today, inspect uncommitted status/diff only when useful and label it as in progress. - Use user notes as evidence but never invent completed work. Mark irreducible uncertainty or request the minimum missing context.
- Return exactly:
# Work Log - <concrete date range>
- <high-impact work item>
- <progress, blocker, or follow-up>
Keep one flat bullet list, ordered by likely team/customer impact, risk reduction, unblockers, and follow-ups before low-level implementation detail. Use concrete dates, not relative labels.
Related Skills
narumiruna/scoring-agent-skills
development
VerifiedTrustedCommunity
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
8SKILL.mdUpdated Jul 29, 2026
narumiruna/improving-codebase-architecture
development
VerifiedTrustedCommunity
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
8SKILL.mdUpdated Jul 29, 2026
narumiruna/auditing-code-security
development
VerifiedTrustedCommunity
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
8SKILL.mdUpdated Jul 29, 2026
narumiruna/running-panel-review-loops
development
VerifiedTrustedCommunity
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.
8SKILL.mdUpdated Jul 26, 2026