Claude Skills by blockscout

github.com/blockscout

40 skillsA× 402 installs64 views

Gh Issue BugAGenerate a structured bug report for GitHub issues based on conversation context about bugs, errors, or broken functionalitytoolsbashgitVotes: 0GitHub stars: 232
Gh Issue ImprovementAGenerate a structured improvement/enhancement proposal for GitHub issues based on conversation contexttoolsbashgitVotes: 0GitHub stars: 232
Gh Issue PublishAPublish a GitHub issue from a markdown file in tmp/gh-issues/ created by gh-issue-bug or gh-issue-improvement skillsdevelopmentgitVotes: 0GitHub stars: 232
Implementation PlanATurn an approved task-analysis result into a shared technical design and coding-ready implementation handoff; use when Claude has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan.md` and `coding-task.md` before writing codedevelopmentrustrailsVotes: 0GitHub stars: 232
Pr DescriptionAPrepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot. Use when Claude needs to draft or refresh a Markdown PR description before review, handoff, or merge, including implementation summary, API changes, environment or configuration changes, database or migration impact, testing, and rollout notes.developmentgorailsVotes: 0GitHub stars: 232
Research ScopeAInvestigate and document the intended scope of a codebase topic through interactive discussion, then persist a durable research note under .memory-bank/research/ once the human confirms the framingdevelopmentVotes: 0GitHub stars: 232
Skills DirectorySkills Directory Look up any of 103,619 scanned skills — grade, score, and every finding. Free.Check a skill
Solution ReviewAReview already-applied code changes against the original task statement or task folder artifacts under `tmp/tasks/<task-name>/`. Use when implementation work is done and Claude must verify scope coverage, detect mismatches or regressions, assess verification gaps, and write a review summary before handoff or merge.developmentgorailsVotes: 0GitHub stars: 232
Task AnalysisAReview a task, issue, or feature request before coding; persist the task framing under `tmp/tasks/<task-name>/task.md`, write one or more `solution_N.md` option files, compare them in `solutions.md` when needed, and recommend a path with explicit reasoningdevelopmentrailsVotes: 0GitHub stars: 232
Task To CodeAApply code changes from an existing task handoff under `tmp/tasks/<task-name>/coding-task-X.md`. Use when Claude receives a task name and coding-task index and must implement that prepared coding task strictly, without inventing missing scope or design details.developmentgorailsVotes: 0GitHub stars: 232
Gh Issue BugADraft a GitHub bug report from the current conversation, save it under tmp/gh-issues/, and follow the repository's canonical bug-report workflow.developmentrailsgitVotes: 0GitHub stars: 232
Gh Issue ImprovementADraft a GitHub improvement or enhancement proposal from the current conversation, save it under tmp/gh-issues/, and follow the repository's canonical improvement workflow.developmentrailsgitVotes: 0GitHub stars: 232
Gh Issue PublishAPublish a drafted GitHub issue from tmp/gh-issues/ by running the repository's gh CLI publish script and relaying the resulting URL or remediation.developmentrailsgitVotes: 0GitHub stars: 232
Implementation PlanATurn an approved task-analysis result into a shared technical design and coding-ready implementation handoff. Use when Codex has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan-X.md` and `coding-task-X.md` before writing code.developmentrustgoVotes: 0GitHub stars: 232
Pr DescriptionAPrepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot. Use when Codex needs to draft or refresh a Markdown PR description before review, handoff, or merge, including implementation summary, API changes, environment or configuration changes, database or migration impact, testing, and rollout notes.developmentgorailsVotes: 0GitHub stars: 232
Research ScopeAInvestigate the intended scope of a codebase topic through discussion with a human, propose a research-note outline, and only create a .memory-bank/research file after explicit human confirmation.developmentgorailsVotes: 0GitHub stars: 232
Solution ReviewAReview already-applied code changes against the original task statement or task folder artifacts under `tmp/tasks/<task-name>/`. Use when implementation work is done and Codex must verify scope coverage, detect mismatches or regressions, assess verification gaps, and write a review summary before handoff or merge.testinggorailsVotes: 0GitHub stars: 232
Task AnalysisAAnalyze an input task, issue, or feature request against the existing codebase, persist the task framing under `tmp/tasks/<task-name>/task.md`, write one or more `solution_N.md` option files, align evaluation criteria with a human when tradeoffs exist, and recommend a path with explicit reasoning.developmentgorailsVotes: 0GitHub stars: 232
Task To CodeAApply code changes from an existing task handoff under `tmp/tasks/<task-name>/coding-task-X.md`. Use when Codex receives a task name and coding-task index and must implement that prepared coding task strictly, without inventing missing scope or design details.developmentgorailsVotes: 0GitHub stars: 232
Implementation PlanATurn an approved task-analysis result into a shared technical design and coding-ready implementation handoff. Use when Cursor has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan.md` and `coding-task.md` before writing code.developmentrustgoVotes: 0GitHub stars: 232
Pr DescriptionAPrepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot. Use when drafting or refreshing a Markdown PR description before review, handoff, or merge, including implementation summary, API changes, environment or configuration changes, database or migration impact, testing, and rollout notes.developmentgorailsVotes: 0GitHub stars: 232
Solution ReviewAReview already-applied code changes against the original task statement or task folder artifacts under `tmp/tasks/<task-name>/`. Use when implementation work is done and you must verify scope coverage, detect mismatches or regressions, assess verification gaps, and write a review summary before handoff or merge.testinggorailsVotes: 0GitHub stars: 232
Task To CodeAApply code changes from an existing task handoff under `tmp/tasks/<task-name>/coding-task-X.md`. Use when you have a task name and coding-task index and must implement that prepared coding task strictly, without inventing missing scope or design details.developmentgorailsVotes: 0GitHub stars: 232
Implementation PlanATurn an approved task-analysis result into a shared technical design and coding-ready implementation handoff; use when Claude has an existing task folder under `tmp/tasks/`, plus a selected solution and related codebase research, and needs to produce `implementation-plan.md` and `coding-task.md` before writing codedevelopmentrustrailsVotes: 0GitHub stars: 232
Pr DescriptionAPrepare a pull request description from task artifacts under `tmp/tasks/<task-name>/` and the current implementation snapshot. Use when Claude needs to draft or refresh a Markdown PR description before review, handoff, or merge, including implementation summary, API changes, environment or configuration changes, database or migration impact, testing, and rollout notes.developmentgorailsVotes: 0GitHub stars: 232
Research ScopeAInvestigate and document the intended scope of a codebase topic through interactive discussion, then persist a durable research note under .memory-bank/research/ once the human confirms the framingdevelopmentVotes: 0GitHub stars: 232
Solution ReviewAReview already-applied code changes against the original task statement or task folder artifacts under `tmp/tasks/<task-name>/`. Use when implementation work is done and Claude must verify scope coverage, detect mismatches or regressions, assess verification gaps, and write a review summary before handoff or merge.testinggorailsVotes: 0GitHub stars: 232
Task To CodeAApply code changes from an existing task handoff under `tmp/tasks/<task-name>/coding-task-X.md`. Use when Claude receives a task name and coding-task index and must implement that prepared coding task strictly, without inventing missing scope or design details.developmentgorailsVotes: 0GitHub stars: 232
Implementation PlanATurn an approved task analysis and selected solution into a technical design and coding-ready handoff under `tmp/tasks/<task-name>/`, with explicit human confirmation before the coding task is written.developmentVotes: 0GitHub stars: 232
Pr DescriptionADraft or refresh a reviewer-facing Markdown PR description from `tmp/tasks/<task-name>/` and the current implementation snapshot, covering functional scope, API/config, migration, testing, and follow-ups.testingtestingapiVotes: 0GitHub stars: 232
Research ScopeAInvestigate and clarify a reusable codebase topic through dialogue, then create or update a `.memory-bank/research` note only after explicit human confirmation.developmentVotes: 0GitHub stars: 232
Solution ReviewAReview applied changes against the original task and artifacts under `tmp/tasks/<task-name>/`, identify scope mismatches, regressions, and verification gaps, and write a review before handoff or merge.developmentVotes: 0GitHub stars: 232
Task AnalysisAAnalyze a non-trivial task against the current codebase, persist task framing and viable solutions under `tmp/tasks/<task-name>/`, align tradeoff criteria with a human, and recommend a path.developmentVotes: 0GitHub stars: 232
Task To CodeAImplement a prepared `tmp/tasks/<task-name>/coding-task-X.md` exactly, validating the result without inventing missing scope or design decisions.developmentVotes: 0GitHub stars: 232
Implementation PlanATurn an approved task analysis and selected solution into a technical design and coding-ready handoff under `tmp/tasks/<task-name>/`, with explicit human confirmation before the coding task is written.developmentapiVotes: 0GitHub stars: 232
Research ScopeAInvestigate and clarify a reusable codebase topic through dialogue, then create or update a `.memory-bank/research` note only after explicit human confirmation.developmentgoapiVotes: 0GitHub stars: 232
Solution ReviewAReview applied changes against the original task and artifacts under `tmp/tasks/<task-name>/`, identify scope mismatches, regressions, and verification gaps, and write a review before handoff or merge.testingVotes: 0GitHub stars: 232
Task AnalysisAAnalyze a non-trivial task against the current codebase, persist task framing and viable solutions under `tmp/tasks/<task-name>/`, align tradeoff criteria with a human, and recommend a path.developmentVotes: 0GitHub stars: 232
Task To CodeAImplement a prepared `tmp/tasks/<task-name>/coding-task-X.md` exactly, validating the result without inventing missing scope or design decisions.developmentVotes: 0GitHub stars: 232
Task AnalysisAReview a task, issue, or feature request before coding; persist the task framing under `tmp/tasks/<task-name>/task.md`, write one or more `solution_N.md` option files, compare them in `solutions.md` when needed, and recommend a path with explicit reasoningdevelopmentrailsVotes: 0GitHub stars: 231
Pr DescriptionADraft or refresh a reviewer-facing Markdown PR description from `tmp/tasks/<task-name>/` and the current implementation snapshot, covering functional scope, API/config, migration, testing, and follow-ups.developmenttestingapiVotes: 0GitHub stars: 231