w-docs
77Document Code Changes Clearly
Documentation updates often land in the wrong file or duplicate existing information. This skill directs the assistant to the owning documentation layer and keeps project guidance consistent.
Review Completed Work and Improve Next Time
Teams often finish tasks without recording what changed, what evidence was missing, or what should improve. This skill produces a concise, task-specific retrospective with up to three practical next steps.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "w-retro" from https://skillstore.io/skills/blockmatic-w-retro.md and its manifest at https://skillstore.io/api/skills/blockmatic-w-retro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "w-retro". We needed to add export filtering. The filter shipped and unit tests passed, but no browser test was run.
Expected outcome:
Requested versus shipped: Export filtering was added and unit-tested. Evidence gap: Browser behavior was not checked. Next change: Add one browser test for filter selection and downloaded results.
Using "w-retro". The task was to update the onboarding guide. The guide changed, but the examples were not checked against the current interface.
Expected outcome:
The scanned skill is a 12-line, chat-only retrospective checklist with no executable code or detected security patterns. No prompt-injection, data-exfiltration, or business-logic abuse evidence was found in SKILL.md.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/blockmatic-w-retro/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/blockmatic-w-retro?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/blockmatic-w-retro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/blockmatic-w-retro/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/blockmatic-w-retro.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>blockmatic. (2026). w-retro security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/blockmatic-w-retro/audits/1@techreport{blockmatic-blockmatic-w-retro-2026,
author = {blockmatic},
title = {w-retro security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/blockmatic-w-retro/audits/1},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "w-retro security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "blockmatic"
date-released: "2026-09-20"
url: "https://skillstore.io/skills/blockmatic-w-retro/audits/1"
identifiers:
- type: other
value: "skillstore:blockmatic-w-retro:audit:1"
description: "Skillstore immutable audit report identifier"
Review the request, shipped changes, checks, and documentation before closing a coding task.
Capture specific process gaps after a sprint item, project milestone, or cross-functional deliverable.
Compare the requested work with the AI-produced result and record better checks for the next session.
Review the completed task in this conversation. State what was requested, what shipped, and one improvement for next time.
Run a retrospective on this completed task. Identify skipped checks, unclear requirements, extra scope, and missing documentation. Suggest no more than three specific changes.
Compare the original request, plan, implementation, and validation evidence. Explain the most important differences and recommend up to three changes for the next similar task.
Perform a task-specific retrospective of this AI-assisted delivery. Separate outcome gaps from process gaps, cite the available evidence, and prioritize three changes that would improve the next session.
Author
blockmaticLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7cd60e5c44d39477abb7a2c00ae0de2cf2a01392
Maintenance freshness
9/20/2026
Usage
0 downloads ยท 0 views
File structure
๐ SKILL.md
Document Code Changes Clearly
Documentation updates often land in the wrong file or duplicate existing information. This skill directs the assistant to the owning documentation layer and keeps project guidance consistent.
Map Code and Architecture with Mermaid
Complex code and documentation can be difficult to understand quickly. This skill turns inspected relationships, flows, and structures into focused Mermaid diagrams.
Refresh API Docs from Source Schemas
API documentation can drift from the schemas and routes that define actual behavior. This skill guides updates from the owning source and keeps generated artifacts out of manual edits.
Review Release Impact Before You Ship
Release changes can miss affected packages, generated templates, tests, or required adopter actions. This skill structures a focused review of release impact, changelog updates, classification, and human approval gates.
Onboard Developers to a Running Local App
New developers often need a reliable path from a cloned repository to a working application. This skill turns project documentation into a focused setup, environment, verification, and handoff workflow.
Run and Fix Project Lint Errors
Lint issues can slow development and leave code quality problems unresolved. This skill runs the project lint workflow, applies small fixes, and checks the result again.
Run Better Sprint Retrospectives
by supercent-io
Sprint teams need structured reflection to turn issues into practical improvements. This skill guides Claude, Codex, or Claude Code through retrospective formats, action items, and follow-up practices.
Track Long Tasks With a Portable State Ledger
by glenskii
Long technical tasks lose decisions, evidence, and next actions across sessions. This skill maintains a concise Markdown state file with reviewed local evidence references.
Verify AI Deliverables with Evidence
by jadeyingwah
AI work can appear complete before the result is opened, tested, or checked against the request. This skill adds staged planning, real-environment verification, and honest completion levels.
Choose the Right AI Tool for Every Task
by 0xDarkMatter
Choosing between many skills and agents can delay technical work. This skill maps each task to focused tools using concise catalogs and selection rules.
Optimize Prompts With Proven Patterns
by wshobson
LLM prompts can fail through unclear instructions, weak examples, or missing evaluation. This skill provides templates, reasoning patterns, and optimization workflows for Claude, Codex, and Claude Code.
Organize GitHub Issues With Labels
by C0ntr0lledCha0s
Large repositories can lose track of issue priority, scope, and release status. This skill designs label taxonomies, applies labels in bulk, and manages milestones with GitHub CLI workflows.