DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to repair a repository issue with a verified, source-backed map with J Space Cognition Suite

Run a high-level pass that maps the code, makes the fix, and gates delivery on evidence.

Authorization notice. J Space Cognition Suite is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer or AI agent assigned to fix a bug or change behavior across several files in an existing repository.

The problemLong repository edits drift from the code, and it is easy to ship without checking the original contracts or tests.

The outcomeA repaired repository with a semantic map tied to inspected files, recorded verification, and a ship check that exits 0 only when the required state is present.

What you need first

  • A host that can load a local SKILL.md and retrieve its supporting files
  • Python 3.10 or later, using the python, python3, or py -3 command for your system
  • A copy of the complete j-space/ directory placed in the host's Skills directory
  • Access to the target project as a task directory, and permission for the host to run local commands
  • For xhigh work, a host that can actually launch child agents

Steps

  1. Copy the complete j-space/ directory into your host's Skills directory and run /scripts/verify_suite.py with your Python 3.10+ command, replacing the path prefix with the installed skill directory.
  2. Initialize the task with /scripts/control.py init --goal "Acceptance criteria" --next "Inspect entry points" --level high --module modules/repository.md, then run /scripts/control.py read --agent root.
  3. Write repo-map.json from files you actually inspected, then run /scripts/control.py repo sync --map repo-map.json and /scripts/control.py repo view --agent root.
  4. Make the change, run the relevant tests, and record real results in evidence/root.txt and a separate checklist in evidence/completion.txt.
  5. Submit /scripts/control.py report --agent root --round 1 --summary "Observed repair and coverage" --evidence evidence/root.txt --completion evidence/completion.txt --source <file> --next "Deliver checked result", sync and view the map again, then run /scripts/control.py check --stage ship. (inferred, check the README)

Prompt for your agent

Use the j-space skill at high level to repair the issue described in <issue file> in the repository at <repo path>. Keep a source-backed repo map, run the relevant tests, and finish with evidence against each acceptance requirement. Verify that `check --stage ship` exits with status 0 before you report completion.

Caveat. The suite provides gates and memory but does not run your tests or grant tool access; the host must supply those.

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