lightforgelabsstudio/findings
skills/findings/SKILL.md
Write reviewer findings to a <slug>.findings.md file for any scoped review target.
documentation
Updated May 7, 2026
$ install --global
skillsauthnpx skillsauth add lightforgelabsstudio/aide findingsInstall 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: May 7, 2026, 6:53 AM140.9s1 file scanned
SKILL.md
- name:
- findings
- description:
- Write reviewer findings to a <slug>.findings.md file for any scoped review target.
Findings
Write reviewer findings for any scoped target using a two-file message bus. This command applies to a file, ADR, doc set, PR context, diff, uncommitted workspace, or another named review scope.
Protocol
<slug>.findings.md— owned by the reviewer; primary output of this command; deleted on acceptance<slug>.response.md— owned by the author; deleted on acceptance
Inputs
- Review target or scope
- Slug for the exchange files
- Optional existing
<slug>.response.mdwhen iterating
Reviewer workflow
- Read the target under review. If
<slug>.response.mdalready exists, read it before revising findings. - Write findings to
<slug>.findings.md:# Review: <target name> ## Findings ### Critical - [path:line or section] Issue. Suggested fix. ### Major / Minor - ... ## Decision: Request Changes | Approve - Tell the author: "findings written to
<slug>.findings.md."
Do not stop at chat-only review output. The findings file is the contract.
Author workflow
- Read
<slug>.findings.md. - For each finding: fix, defer (with reason), or reject (with reason).
- Write response to
<slug>.response.md:# Response: <target name> ## Responses - [Finding ref] Fixed | Deferred: <reason> | Rejected: <reason> ## Target status: Revised | Accepted as-is - Tell the reviewer: "response written to
<slug>.response.md."
Closing the loop
Reviewer reads <slug>.response.md. If satisfied: both files deleted, target accepted. If not: iterate.
Notes
- Use a stable slug for the review scope:
pr-524,workspace-uncommitted,movement-system,2026-03-01-network-flow-logistics-system. - Use
<issue-number>-<slug>naming when the review is tied to a GitHub issue. - This protocol is relay-agnostic; future tooling can automate the file exchange.
Related Skills
lightforgelabsstudio/sanity-check
testing
VerifiedTrustedCommunity
Skeptical gap analysis for issues, ADRs, plans, and docs. Use when the user wants a second-pass check for missing decisions, contradictions, edge cases, hidden dependencies, scope drift, or readiness before implementation.
SKILL.mdUpdated May 11, 2026
lightforgelabsstudio/sync
tools
VerifiedTrustedCommunity
Sync branch with remote and confirm a clean end-of-session state.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/skill-author
testing
VerifiedTrustedCommunity
Create or update an AIDE skill in .aide/skills with valid frontmatter and a concise workflow.
SKILL.mdUpdated May 7, 2026
lightforgelabsstudio/scope
tools
VerifiedTrustedCommunity
Decompose an accepted ADR into GitHub issues using the issue-creator tool.
SKILL.mdUpdated May 7, 2026