- Skills
- 156
- 仓库
- 1
- 职业覆盖
- 0
- 场景覆盖
- 0
- Stars
- ★ 1
Anderson Rodrigues 的 Skills 156
sample-skill
Does a sample task. Use when a sample is needed.
unexplained-contract
Does a sample task. Use when a sample is needed.
shell-block
Does a sample task. Use when a sample is needed.
project-identifier
Does a sample task. Use when a sample is needed.
oversized
Does a sample task. Use when a sample is needed.
no-activation
Does a sample task.
names-technology
Runs the pytest suite. Use when testing.
copies-rule
Does a sample task. Use when a sample is needed.
change-without-verification
Does a sample task. Use when a sample is needed.
update
Paved command paved.update. Plan and apply a compatible local Paved Core, adapter or input update. Use when the user asks to update initialized Paved state.
unit-testing
Write fast, isolated tests for one unit of logic using the repository's test conventions. Use when new or changed logic can be proven without real external collaborators; use integration-testing when behavior depends on a boundary.
threat-modeling
Identify assets, trust boundaries, likely threats and mitigations in a proposed design. Use when designing a new component, interface, data flow, integration or handling of sensitive data, or when the user asks for a threat model; use security-review for a completed code change.
task-specification
Turn a repository change request into a grounded, actionable task with a clear outcome and verifiable acceptance criteria. Use when asked to draft or complete a new or sparse issue, ticket, story, bug report or epic; use task-review to assess existing work-item text.
task-review
Review an existing task, issue, ticket, story, bug report or epic for missing context, unsupported assumptions, unverifiable criteria and scope. Use when asked to assess or refine work-item text before implementation; use task-specification to write a new item and change-review to review code.
status
Paved command paved.status. Inspect Paved setup, diagnostics and open runs, then offer safe repairs. Use when checking readiness or deciding whether a reported Paved problem needs repair.
security-review
Review a change for risks to trust boundaries, input handling, access control, secrets, sensitive data or dependencies. Use when a change affects input, authorization, data exposure, security configuration or dependencies; use threat-modeling for a design before it is built.
runtime-debugging
Diagnose behavior that appears only while a system is running using logs, metrics, traces and health signals, starting with read-only inspection. Use when code inspection cannot explain a live defect or incident.
root-cause-analysis
Identify and confirm the cause of a defect from errors, logs, failing checks or reproduction evidence without implementing a fix. Use when the user asks why a failure happens or the cause is still uncertain; use bug-investigation when a verified fix is expected.