Use when the user explicitly authorizes Git or publication actions: verify repository state, then commit, push, open a pull request, tag, release, or deploy only as authorized.
sbusso/coderkit
SkillsMP has collected 12 skills from sbusso/coderkit. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 12
- GitHub stars
- 2
- GitHub forks
- 0
Skills in this repository
Showing 12 of 12 collected skills.
Use for non-trivial unexpected behavior or reported defects that require causal investigation: reproduce the issue, trace the real path, and isolate the root cause before an authorized fix.
Use when a substantive development request has meaningful solution uncertainty: trace real flows, compare genuinely different approaches, and choose a direction. Skip when the path is already clear.
Use for substantive code changes where a structured build loop adds value. Implement the approved request or plan with proportionate verification; skip for trivial edits.
Use when complexity, risk, or multiple dependent units justify a durable implementation plan. Skip for small, already-clear changes.
Use when the user requests a review or when change risk justifies an independent verification pass: run real checks and assess correctness, security, and regressions.
Use when the user explicitly authorizes Git or publication actions: verify repository state, then commit, push, open a pull request, tag, release, or deploy only as authorized.
Use for non-trivial unexpected behavior or reported defects that require causal investigation: reproduce the issue, trace the real path, and isolate the root cause before an authorized fix.
Use when a substantive development request has meaningful solution uncertainty: trace real flows, compare genuinely different approaches, and choose a direction. Skip when the path is already clear.
Use for substantive code changes where a structured build loop adds value. Implement the approved request or plan with proportionate verification; skip for trivial edits.
Use when complexity, risk, or multiple dependent units justify a durable implementation plan. Skip for small, already-clear changes.
Use when the user requests a review or when change risk justifies an independent verification pass: run real checks and assess correctness, security, and regressions.