All authors

Claude Skills by leszekgruchala
github.com/leszekgruchala10 skills2 installs8 views
- Archive WorklogsArchive dated `.ai/worklog` development worklogs by year. Use to archive, clean up, organize, or move worklogs older than a date or number of days. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- DevelopOrchestrate non-trivial coding through needed research, optional innovation, decision-settling spec, implementation, validation, independent review, and remediation. Use for end-to-end changes with unclear decisions, multiple files/projects, meaningful risk, or delegable phases.Votes: 0GitHub stars: 5
- ImplementImplement or fix decision-complete code directly, or execute an approved spec phase with verification. Use for build/fix requests or an approved spec path; route unresolved product or architecture decisions to spec. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- InnovateExplore meaningfully different solution directions and trade-offs without selecting or implementing one. Use when the user or develop requests alternatives before spec; prior research is optional. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- ResearchInvestigate code, behavior, documentation, or technical facts without proposing or choosing changes. Use for research-only requests, codebase understanding, flow tracing, comparisons, and bounded fact collection; route change decisions to spec. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- Review CodeReview a requested local change for evidence-backed defects, return actionable findings directly to the caller, and promote only confirmed prevention rules. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- SpecSettle product decisions and create a decision-complete implementation specification with phases, boundaries, dependencies, and verification. Use for specs, detailed/execution/phased implementation plans, or decisions needed before implementation; prefer over native planning workflows. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- Test RunnerDiscover, run, and report change validation without modifying the workspace. Use for tests, lint, formatting, type checks, builds, or independent verification while another agent owns fixes. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- BrainstormExplore and pressure-test an idea through a short back-and-forth discussion about purpose, value, scope, and possible directions. Document worthwhile ideas once enough useful information emerges or the user asks to save. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5
- Change ReportValidate a pull request or branch diff and create a concise HTML explanation of its purpose, practical impact, and material architecture changes with before/after comparisons. Use for visual change reports and change walkthroughs. Remain active for follow-ups until an explicit user request or the calling `develop` orchestrator selects another skill.Votes: 0GitHub stars: 5