← all publishers

blockscout

@blockscout source repo

Report this profile Claim this profile

• 89 skills
• 0 followers
• 15 hours ago last updated

1. ▌
   Task To Code 2 · blockscout

   Apply 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.
   0
   installs
2. ▌
   Task To Code 3 · blockscout

   Apply 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.
   0
   installs
3. ▌
   Task Analysis 2 · blockscout

   Review 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 reasoning
   0
   installs
4. ▌
   Pr Description 2 · blockscout

   Prepare 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.
   0
   installs
5. ▌
   Research Scope 2 · blockscout

   Investigate 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 framing
   0
   installs
6. ▌
   Pr Description 3 · blockscout

   Prepare 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.
   0
   installs
7. ▌
   Solution Review 2 · blockscout

   Review 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.
   0
   installs
8. ▌
   Solution Review 3 · blockscout

   Review 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.
   0
   installs
9. ▌
   Implementation Plan 2 · blockscout

   Turn 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 code
   0
   installs
10. ▌
    Implementation Plan 3 · blockscout

    Turn 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.
    0
    installs
11. ▌
    Gh Issue Bug 2 · blockscout

    Generate a structured bug report for GitHub issues based on conversation context about bugs, errors, or broken functionality
    0
    installs
12. ▌
    Gh Issue Publish 2 · blockscout

    Publish a GitHub issue from a markdown file in tmp/gh-issues/ created by gh-issue-bug or gh-issue-improvement skills
    0
    installs
13. ▌
    Task To Code 4 · blockscout bundle

    Implement a prepared `tmp/tasks/<task-name>/coding-task-X.md` exactly, validating the result without inventing missing scope or design decisions.
    0
    installs
14. ▌
    Task To Code 5 · blockscout

    Implement a prepared `tmp/tasks/<task-name>/coding-task-X.md` exactly, validating the result without inventing missing scope or design decisions.
    0
    installs
15. ▌
    Task Analysis 3 · blockscout bundle

    Analyze 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.
    0
    installs
16. ▌
    Task Analysis 4 · blockscout

    Analyze 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.
    0
    installs
17. ▌
    Pr Description 4 · blockscout bundle

    Draft 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.
    0
    installs
18. ▌
    Research Scope 3 · blockscout bundle

    Investigate and clarify a reusable codebase topic through dialogue, then create or update a `.memory-bank/research` note only after explicit human confirmation.
    2
    installs
19. ▌
    Pr Description 5 · blockscout

    Draft 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.
    0
    installs
20. ▌
    Research Scope 4 · blockscout

    Investigate and clarify a reusable codebase topic through dialogue, then create or update a `.memory-bank/research` note only after explicit human confirmation.
    0
    installs
21. ▌
    Solution Review 4 · blockscout bundle

    Review 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.
    0
    installs
22. ▌
    Gh Issue Improvement 2 · blockscout

    Generate a structured improvement/enhancement proposal for GitHub issues based on conversation context
    0
    installs
23. ▌
    Solution Review 5 · blockscout

    Review 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.
    0
    installs
24. ▌
    Implementation Plan 4 · blockscout bundle

    Turn 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.
    0
    installs
25. ▌
    Implementation Plan 5 · blockscout

    Turn 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.
    0
    installs
26. ▌
    Web3 Dev · blockscout bundle

    Build web3 applications, scripts, CLIs, bots, mobile apps, and desktop apps that need blockchain data via the Blockscout PRO API — a single HTTP API spanning 100+ EVM chains. Invoke this skill whenever the user wants to read blockchain data over HTTP (transactions, blocks, addresses, tokens, NFTs, logs, contract context, internal txs, account abstraction, etc.) and is building software that calls an API directly. Trigger on direct mentions of `Blockscout PRO API`, `pro-api`, `proapi_`, `Blockscout API`, `block explorer API`, `api.blockscout.com`, or on broader phrasing like "build a web3 app", "index/query on-chain data", "wallet history", "NFT inventory", "transaction logs across chains", "how much does the Blockscout API cost", "chain IDs supported by Blockscout". Use this skill for direct HTTP integrations; the sibling `blockscout-analysis` skill covers the Blockscout MCP Server.
    0
    installs
27. ▌
    Blockscout Analysis · blockscout bundle

    MANDATORY — invoke this skill BEFORE making any Blockscout MCP tool calls or writing any blockchain data scripts, even when the Blockscout MCP server is already configured. Provides architectural rules, execution-strategy decisions, MCP REST API conventions for scripts, endpoint reference files, response transformation requirements, and output conventions that are not available from MCP tool descriptions alone. Use when the user asks about on-chain data, blockchain analysis, wallet balances, token transfers, contract interactions, on-chain metrics, wants to use the Blockscout API, or needs to build software that retrieves blockchain data via Blockscout. Covers all EVM chains.
    0
    installs
28. ▌
    Bump Skill Version · blockscout bundle

    Bump a skill's version number across all files in this repo (the skill's own frontmatter, the marketplace plugin entry, and any skill-specific occurrences). Pass the skill name and new version as arguments (e.g., 'blockscout-analysis 0.5.0'). Use after content changes are complete and the skill is ready for a new release.
    0
    installs
29. ▌
    Upgrade Blockscout API · blockscout bundle

    Refresh the bundled Blockscout API reference files inside one of this repo's end-user skills. Takes a target argument; each target has its own pipeline because the source artefacts differ (Swagger releases for `blockscout-analysis`, a build-time clone of the `pro-api` repo for `web3-dev`). Run when a target's upstream cuts a new release and the skill's bundled references need to catch up.
    0
    installs
30. ▌
    Openapi Spec · blockscout bundle

    Create, adjust, or inspect OpenAPI declarations for Blockscout API v2 endpoints. Use this skill whenever the user asks to: add an OpenAPI spec to an endpoint that lacks one, update a spec after controller/view changes, audit or fix an existing OpenAPI declaration, or work with open_api_spex annotations in the Blockscout codebase. Also trigger when the user mentions 'swagger', 'openapi', 'open_api_spex', 'API spec', 'API schema', or 'operation macro', or when debugging failures like 'response schema mismatch', 'CastAndValidate rejection', 'json_response validation error', 'Unexpected field', or extra/missing keys in API responses.
    0
    installs
31. ▌
    Ecto Migration · blockscout

    Generates Ecto migrations for the Blockscout Elixir project using mix ecto.gen.migration command. Use when you need to create database schema changes, add tables, modify columns, or manage database structure.
    0
    installs
32. ▌
    Code Formatting · blockscout

    Fixes code formatting in the Blockscout Elixir project using mix format. Use when you need to fix formatting violations, code style inconsistencies, or ensure consistent code formatting. For linting issues, use `mix credo`. Use this skill for every change made.
    0
    installs
33. ▌
    Compile Project · blockscout

    Compile the Blockscout Elixir project to verify all dependencies and code changes work correctly. Use this skill before finalizing changes to ensure the project builds successfully without errors.
    0
    installs
34. ▌
    Alias Nested Modules · blockscout

    Define module aliases at the top of the file instead of using fully qualified nested module names in function bodies. Improves code readability and maintainability while addressing Credo style warnings.
    0
    installs
35. ▌
    With To Case Refactor · blockscout

    Replace `with` expressions that contain only a single `<-` clause and an `else` branch with a `case` expression. This addresses the Credo warning "with contains only one <- clause and an else branch, consider using case instead" and produces cleaner, more idiomatic Elixir code.
    0
    installs
36. ▌
    Elixir Clause Grouping · blockscout

    Use when refactoring Elixir multi-clause functions, extracting helper functions, or fixing Credo readability warnings caused by placing `defp` helpers between clauses of the same function. Keeps function clauses contiguous and moves helpers below the full clause group.
    0
    installs
37. ▌
    Efficient List Building · blockscout

    Build lists efficiently using prepend operations and Enum.reverse/1 instead of append. Appending to lists is O(n) while prepending is O(1). Use [head | tail] notation and reverse at the end when order matters.
    0
    installs
38. ▌
    Heavy DB Index Operation · blockscout

    Generate background migration modules for creating, dropping, or renaming database indexes on large tables using the Explorer.Migrator.HeavyDbIndexOperation framework. Automatically updates the BackgroundMigrations cache module with proper tracking. These migrations run in the background with progress tracking and dependency management. Use this skill for requests on creating background migrations to delete / create / rename indexes on large tables (logs, internal_transactions, token_transfers, addresses, transactions, blocks, etc.) to avoid blocking the database.
    0
    installs
39. ▌
    Compare Against Empty List · blockscout

    Optimize list checks by comparing against empty lists instead of using length/1. Avoid expensive list traversal operations when checking if a list is empty or has elements. Use pattern matching or empty list comparison for better performance.
    0
    installs
40. ▌
    Update Common Blockscout Env · blockscout

    Ensure every newly introduced environment variable is also added to docker-compose/envs/common-blockscout.env so local Docker setups stay aligned with runtime configuration.
    0
    installs
41. ▌
    Elixir Credo Predicate Naming · blockscout

    Use when working on Elixir code with Credo predicate naming warnings, boolean helper functions, or renaming functions that start with is_. Prevents violations like: Predicate function names should not start with 'is' and should end in a question mark.
    0
    installs
42. ▌
    Alphabetically Ordered Aliases · blockscout

    Ensure that aliases are alphabetically ordered within their groups to maintain consistent code style and address Credo readability warnings.
    0
    installs
43. ▌
    Gh Safe · blockscout bundle

    Use this skill whenever you are about to run any write `gh` CLI command — `gh pr edit`, `gh pr create`, `gh issue edit`, `gh issue create`, `gh pr comment`, `gh issue comment`, `gh pr close`, `gh pr merge`, `gh release create`, or similar. High-level `gh` commands sometimes fail with "missing required scopes" auth errors even though the underlying GitHub REST API works fine with the same token. This skill makes you automatically fall back to `gh api` instead of stopping to ask the user to re-authenticate. Always invoke before running any mutating `gh` command.
    0
    installs
44. ▌
    Plan Export · blockscout bundle

    Export a detailed phased implementation plan for a GitHub issue to a file, reading all applicable rules from .cursor/rules before planning
    0
    installs
45. ▌
    Consult Spec · blockscout bundle

    TRIGGER CONDITIONS - invoke this skill when ANY of these apply: User-triggered (explicit request): - User mentions "specification", "SPEC", "SPEC.md", "spec requirements" - User asks to "verify with spec", "confirm with specification", "check requirements" - User requests "authoritative requirements" or "source of truth" Agent self-triggered (during reasoning): - Before implementing any feature or making code changes - When verifying technical requirements or constraints - When making architectural or design decisions - When you need unbiased guidance not influenced by current implementation - When encountering conflicting information and need ground truth PURPOSE: Consults SPEC.md through an isolated subagent that ONLY reads the specification, never implementation code. This ensures guidance is based on authoritative requirements, not potentially incorrect existing code.
    0
    installs
46. ▌
    Implement Plan · blockscout bundle

    Use to implement a structured implementation plan (e.g. temp/impl_plans/issue-*.md) phase by phase. Trigger when the user asks to implement, execute, realize, or "do" an implementation-plan file. Orchestrates a phase-developer subagent and a plan-correspondence-verifier subagent for each phase, commits each verified phase, then walks the Final Checklist. Invoke explicitly — it makes commits and spawns many subagents.
    0
    installs
47. ▌
    Read Temp File · blockscout bundle

    Reads the content of a file located in the temporary directory (temp/) which is otherwise ignored by git.
    0
    installs
48. ▌
    Describe Changes · blockscout bundle

    Describe very high level changes required to implement discussed functionality (functionality, test, docs)
    0
    installs
49. ▌
    Sepolia Foundry Tx · blockscout bundle

    Use this skill whenever the agent needs to deploy a smart contract to Sepolia testnet via Foundry (`forge create` or `forge script --broadcast`), routed through the Blockscout PRO API's JSON-RPC gateway instead of a third-party RPC provider. Trigger on requests like "deploy this contract to Sepolia", "deploy via Foundry", "broadcast this Foundry deployment script", or any `forge create`/`forge script` invocation that needs a signer and an RPC endpoint for Sepolia (chain id 11155111) in this project. Also consult it to find which local Foundry keystore to sign with — this project stores test signing keys as encrypted keystores under `.ai/wallet/`, never as a plain private key in `.env`. Do not use this for reads (balances, transaction history, contract info) — use the connected Blockscout MCP tools for those directly; this skill is specifically about broadcasting a deployment.
    0
    installs
50. ▌
    Test Guided Tool Run · blockscout bundle

    Use when user asks to "run tool as function", "test directly", or "call standalone" (outside MCP server). Essential for correct mock Context setup (MagicMock + AsyncMock). Finds integration tests with real test data.
    0
    installs
51. ▌
    Address Plan Findings · blockscout bundle

    Validate review findings about an implementation plan against the codebase and repo rules, fix the valid ones in the plan, and write a feedback file noting what changed and what was rejected (and why). For plan-review findings, not code-review findings.
    0
    installs
52. ▌
    Run Integration Tests · blockscout bundle

    Use this skill WHENEVER you are about to run the integration tests of this project — the whole suite, a single module, or one test. This includes any time you would otherwise type `pytest -m integration`, `uv run pytest -m integration`, run anything under `tests/integration/`, or want to check live Blockscout/Chainscout/BENS connectivity. Integration tests make real network calls with no hard HTTP timeout, so one unresponsive endpoint can hang a plain pytest run for an unbounded time and block you. This skill runs each test in an isolated subprocess with a per-test timeout, kills any hung test, and always returns a bounded report flagging which tests timed out or are slow. Prefer it over invoking pytest directly for integration tests.
    0
    installs
53. ▌
    Review Described Changes · blockscout bundle

    Critically review a GitHub issue plus a "described changes" overview written by a developer — open the referenced code, verify the overview's claims against what the code actually does, and report gaps, inconsistencies, and likely mistakes — without modifying any files. Invoke manually.
    0
    installs
54. ▌
    Implementation Plan Review · blockscout bundle

    Expert review of an implementation plan against a GitHub issue/enhancement description (provided as a local file or a GitHub issue URL) and the current repository codebase. Use when asked to critique a plan for correctness, completeness, codebase alignment, risks, and test/rollout readiness (do not implement).
    0
    installs
55. ▌
    Export Plan Review Comments · blockscout bundle

    Export the survived comments from a completed implementation-plan review into a timestamped Markdown findings artifact. Use when the user asks to save, write, or export plan-review comments/findings under `.ai/impl_plans/PLAN_ID/findings/REVIEW_TIMESTAMP/finding.md` while preserving the original review wording and wrapping each finding in paired `comment` markers.
    0
    installs
56. ▌
    Address Code Review Comments · blockscout bundle

    Enter the worktree of a GitHub PR, validate the code-review comments raised on it against what the code actually does and the repo rules, fix the valid ones directly in the PR's source/tests, and report in chat — a brief note per closed comment and a detailed plain-language explanation of every comment left unclosed and why. For code-review comments on a PR. Invoke manually.
    0
    installs
57. ▌
    Review Plan Findings Feedback · blockscout bundle

    Manually review a feedback file produced after implementation-plan review findings were addressed. Use when the user asks to verify that plan changes correctly close, correctly reject, or fail to close the original findings, while checking for newly introduced or newly exposed problems. Independently adjudicates only new candidate problems with the implementation-plan-review protocol, writes surviving unresolved or new findings to the plan-id findings directory, and replies with the output path or a concise no-new-findings status.
    0
    installs
58. ▌
    To Spec · blockscout bundle

    Turn the current conversation into a product-task spec and publish it as a draft PR: no interview, just synthesis of what you've already discussed.
    0
    installs
59. ▌
    Grilling · blockscout

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
    0
    installs
60. ▌
    Create Pr · blockscout

    Create or finalize a pull request — three modes: placeholder draft PR at spec time, finalize a draft into ready-for-review, or a regular PR right away for work done outside the task workflow.
    0
    installs
61. ▌
    Slack File · blockscout bundle

    Download Slack attachments by file ID, or upload local files into a Slack thread. Use when a Slack message lists Files: whose contents matter, or when posting a file to Slack; the MCP connector reports metadata only. Guides Keychain token setup if missing.
    0
    installs
62. ▌
    To Tickets · blockscout bundle

    Break a product-task spec into a set of tracer-bullet tickets, each declaring its blocking edges.
    0
    installs
63. ▌
    Add Env Var · blockscout

    Step-by-step checklist for adding a new NEXT_PUBLIC_* environment variable. Use when introducing any new runtime env var.
    0
    installs
64. ▌
    Deploy Demo · blockscout

    Create a GitHub deployment for the current branch using the deploy-review workflow
    0
    installs
65. ▌
    Slack Watch · blockscout bundle

    Watch Slack threads (DMs and channels) for new replies over a Socket Mode WebSocket, printing one line per genuinely-new reply. Use to be notified inside a live local Claude Code or Cursor session (not a cloud agent).
    0
    installs
66. ▌
    Add New Page · blockscout bundle

    Scaffold a new page (index / detail / general) and optionally wire it to API data. Use when adding any new route to the app, or when wiring API data into an already-scaffolded page (one with `TODO (api-data):` markers).
    0
    installs
67. ▌
    Create Issue · blockscout

    Create a GitHub issue from the available context. Use when the user asks to file an issue from a source they name (Slack thread, notes, document) or from this conversation.
    0
    installs
68. ▌
    Finalize Task · blockscout

    Land a finished product task — prune the working files (keep spec.md), then finalize the draft PR into ready-for-review.
    0
    installs
69. ▌
    Grill The Task · blockscout

    Grill a product task (GitHub issue) into implementable work.
    0
    installs
70. ▌
    Resolve Review · blockscout

    Close out review findings — adjudicate each one, fix what deserves fixing, then reply on the PR threads or in the task's review file.
    0
    installs
71. ▌
    Review Changes · blockscout bundle

    Review a change on three axes — spec compliance, repo standards, correctness — then publish the findings as inline PR comments or into a review file in the task folder.
    0
    installs
72. ▌
    Prepare Release · blockscout bundle

    Prepare the next release of the application (tag, docs, release notes), then publish the pre-release and request a staging roll-up
    0
    installs
73. ▌
    Resolve API Url · blockscout

    Resolve the real request URL of an API resource on a live Blockscout instance (`service:name` + instance → full URL). Use whenever a request must be made to, or a sample response fetched from, a deployed instance's API.
    0
    installs
74. ▌
    Update Glossary · blockscout

    Add a new term, update an existing definition, or remove an outdated entry in `.agents/GLOSSARY.md`. Use whenever the user wants to write something into the project glossary, or asks "should this be in the glossary?". Enforces the file's principle — disambiguation and etymology only, no paths/env vars/UI-location restatements.
    0
    installs
75. ▌
    Add API Resource · blockscout

    Declare new API resource(s) in an existing API service. Use whenever the app needs to call an endpoint that has no `service:name` resource yet.
    0
    installs
76. ▌
    Check Github CLI · blockscout

    Ensure GitHub CLI (gh) is installed and authenticated before running gh commands; guide the user to configure it if not
    0
    installs
77. ▌
    Implement Ticket · blockscout

    Execute one ticket of a product-task spec.
    0
    installs
78. ▌
    Deprecate Env Var · blockscout

    Checklist for deprecating a NEXT_PUBLIC_* environment variable — immediate removal, or a grace period before a later removal. Use when removing, renaming, or replacing a runtime env var.
    0
    installs
79. ▌
    Publish Beta Types · blockscout

    Publish a beta version of a `@blockscout/*-types` npm package and pin it here. Use when a needed response type isn't in any published package version yet.
    0
    installs
80. ▌
    Resolve Config Request · blockscout bundle

    Turn a Slack request into the exact env vars to set on a live instance, and hand them to DevOps.
    0
    installs
81. ▌
    Task To Code · blockscout bundle

    Apply 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.
    0
    installs
82. ▌
    Task Analysis · blockscout bundle

    Analyze 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.
    0
    installs
83. ▌
    Pr Description · blockscout bundle

    Prepare 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.
    0
    installs
84. ▌
    Research Scope · blockscout bundle

    Investigate 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.
    0
    installs
85. ▌
    Solution Review · blockscout bundle

    Review 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.
    0
    installs
86. ▌
    Implementation Plan · blockscout bundle

    Turn 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.
    0
    installs
87. ▌
    Gh Issue Bug · blockscout bundle

    Draft a GitHub bug report from the current conversation, save it under tmp/gh-issues/, and follow the repository's canonical bug-report workflow.
    0
    installs
88. ▌
    Gh Issue Publish · blockscout bundle

    Publish a drafted GitHub issue from tmp/gh-issues/ by running the repository's gh CLI publish script and relaying the resulting URL or remediation.
    0
    installs
89. ▌
    Gh Issue Improvement · blockscout bundle

    Draft a GitHub improvement or enhancement proposal from the current conversation, save it under tmp/gh-issues/, and follow the repository's canonical improvement workflow.
    0
    installs