Produce a numbered findings assessment with evidence-backed observations and file references.
npx skills add https://github.com/bkudria/cc-plugins --skill assess-bkudria
Please help me install this Agent Skill. Skill: assess Source: https://github.com/bkudria/cc-plugins/tree/main/plugins/triage/skills/assess Command: npx skills add https://github.com/bkudria/cc-plugins --skill assess-bkudria
Investigate a scope for problems and opportunities and produce a structured, numbered findings assessment that can be consumed by other skills such as iterate.
Run a scope assessment on the provided project and generate a numbered findings report.
High-intent search queries and answers about installing and using this skill.
To investigate a codebase, run a structured assessment that follows a phase-driven workflow of scope resolution, planning, investigation, and synthesis to produce numbered findings with concrete file references.
A phase-based codebase investigation is a structured process that resolves scope, plans exploration, investigates evidence, and synthesizes findings. You need it when auditing configurations or reviewing features to produce actionable, evidence-backed reports.
To structure code review findings, use a numbered assessment format where each observation includes explicit evidence such as file paths, line numbers, or explicit values to support conclusions for later action.
Yes, you can use a structured findings assessment for configuration audits and feature reviews because it applies to any defined scope, generating evidence-backed observations that describe problems and opportunities for future action.
The best way to document codebase problems for future iteration is generating a numbered findings assessment with concrete file references, which can be directly consumed by downstream skills to act upon the evidence-backed observations.
If scope resolution fails during a codebase assessment, the workflow falls back to a scope interview phase to gather the necessary boundaries and context before proceeding to exploration planning and investigation.
jrodrigopucaAnalyze repository structure to define documentation scope and complexity.
BradliebsIdentify and document recurring codebase patterns through targeted observation sessions.
akiselevOrchestrates codebase exploration to produce evidence-backed findings with file:line references.
saschadudkin-sketchAutomate code review for rezidence4/DomHub repository changes.
