[Resource]: aiset

Open Beginner friendly
  • Is something wrong?
#3,380 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
content

Research direction

Start with CONTRIBUTING.md, which the submitter says they have read, and check the repository's existing resource entries for the expected format and placement. Add aiset with its name, link, category, and description in the appropriate collection; done means the resource is listed consistently with the contribution guidelines.

Written by the indexing model from the issue text.

Description

resource-submission validation-passed
Display Name

aiset

Category

Agent Orchestration

Link

https://github.com/JamshidS/aiset

Author Name

JamshidS

Author Link

https://github.com/JamshidS

Description

Turns repositories into a team of Claude Code subagents (a PM, one engineer per repo, QA, an integration checker) with persistent memory, so a new task doesn't start from zero. Per-repo knowledge briefs hold architecture, conventions and pitfalls; when a task closes, the PM records its decisions and gotchas as an episode and adds the lessons to that repo's brief, all as plain editable files. Includes teammap, a code map that answers "where is X and who calls it" in one call.

Checklist
  • I have visited this repo before with my own eyes, and I have confirmed that this resource is sufficiently distinct from any existing resource
  • All links are working and publicly accessible
  • This resource is specific to Claude Code
  • I have read the CONTRIBUTING.md
  • I promise I actually did these things and not doing so is shameful and lazy
  • Do not check the following box - leave it unchecked. By checking this box, I admit that I am not reading any of these statements.
Dominant language
Python
Stars
55.2k
Forks
4.8k
Avg merge
48m
Merged PRs (30d)
54

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hesreallyhim/awesome-claude-code

All issues in hesreallyhim/awesome-claude-code

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.