DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to import all GitHub issues into a local task backlog with Reslop

Pull a repository's issues into Reslop tasks so they sit next to the review plan.

Credentials. Importing issues from a private repository may need access to the hosting service, and the README does not explain how credentials are provided.

Who it is forA maintainer who wants open GitHub or GitLab issues visible in the same place as local review work.

The problemIssues live in the hosting site, so planning a repair means switching between a browser and the terminal.

The outcomeIssues imported as tasks and into the local plan, ready to be ordered and sent to an agent.

What you need first

  • Node.js >=18.15.0 and npm
  • git installed, with the repository you want to review cloned locally
  • Windows Terminal if you are on Windows
  • An ACP-capable agent command on PATH, such as claude-agent-acp or codex-acp, if you want to run a plan in an agent

Steps

  1. Run npm i -g reslop once to install the tool.
  2. Run reslop https://github.com/metarhia/metacom/issues as an example, replacing the URL with your own repository's issues page.
  3. Open the tasks area in the dashboard and review the imported items.
  4. Check the local plan in .plan/ for the issues you chose to keep.

Prompt for your agent

In reslop for the repository at <repo-path>, import the issues from <issues-URL> and list the task titles added to the local plan. Report the number imported. Verify the count matches the open issue count shown on the hosting site.

Caveat. The README says it imports all issues with the issues URL, but it does not state a limit or how closed issues are treated, so check the result against the site.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page