Top 20 GitHub Repositories for Autonomous AI Agents in Software Development
•
2
Luigi PRO
luigi12345
AI & ML interests
None yet
Recent Activity
updated
a collection
about 8 hours ago
animation
liked
a Space
about 10 hours ago
xd11yggy/IDE_Editor_Compiler_Interpreter
updated
a Space
1 day ago
luigi12345/Auto-IOL
Articles
Organizations
None yet
luigi12345's activity
posted
an
update
1 day ago
Post
195
Top 20 GitHub Repositories for Autonomous AI Agents in Software Development
Best AI Software Engineer Agents and AI Frameworks and Tools.
Discover the top 20 GitHub repositories for autonomous AI agents in software development. These tools offer features like automated testing, debugging, and codebase management, complete with user-friendly interfaces. Enhance your development workflow with these cutting-edge resources. Read more: https://huggingface.co/blog/luigi12345/ai-autonomous-agents
Best AI Software Engineer Agents and AI Frameworks and Tools.
Discover the top 20 GitHub repositories for autonomous AI agents in software development. These tools offer features like automated testing, debugging, and codebase management, complete with user-friendly interfaces. Enhance your development workflow with these cutting-edge resources. Read more: https://huggingface.co/blog/luigi12345/ai-autonomous-agents
posted
an
update
3 days ago
Post
3536
MinimalScrap
Only Free Dependencies. Save it.It is quite useful uh.
Only Free Dependencies. Save it.It is quite useful uh.
!pip install googlesearch-python requests
from googlesearch import search
import requests
query = "Glaucoma"
for url in search(f"{query} site:nih.gov filetype:pdf", 20):
if url.endswith(".pdf"):
with open(url.split("/")[-1], "wb") as f: f.write(requests.get(url).content)
print("✅" + url.split("/")[-1])
print("Done!")
Reacted to
their
post with 👍
10 days ago
Post
2288
Best Debug Prompt
You are a frustrated user who has tested this application extensively. Your job is to list EVERY possible way this app could completely break or become unusable.
For each potential failure:
1. What would make you say "This app is totally broken!"?
2. What exact steps did you take when it broke?
3. What did you see on your screen when it broke?
4. How angry would this make a typical user (1-10)?
5. What would you expect the app to do instead?
Think about:
- What happens if you click buttons really fast?
- What if your internet is slow/disconnected?
- What if you upload weird files/images?
- What if you try to break the app on purpose?
- What if multiple people use it at once?
- What if you use it on mobile/tablet?
- What if you refresh/navigate while it's working?
- What if you paste invalid inputs?
- What if you upload HUGE files?
- What if you leave it running overnight?
Don't worry about being technical - just describe what you saw break as a user.
Format each issue like:
ISSUE #1: [Brief angry user description]
- STEPS TO BREAK IT: [Exactly what you did]
- WHAT HAPPENED: [What you saw]
- ANGER LEVEL: [1-10]
- EXPECTED: [What should happen]
Keep going until you've found every possible way to break this app from a user's perspective!
After outpuiting the list, accoring to the list optmiced Composer edit block to fix the ones severe that make sense to adjust accoirng to gradio limitations and current usage target )dont suppose we need unecessary funcitons)
You are a frustrated user who has tested this application extensively. Your job is to list EVERY possible way this app could completely break or become unusable.
For each potential failure:
1. What would make you say "This app is totally broken!"?
2. What exact steps did you take when it broke?
3. What did you see on your screen when it broke?
4. How angry would this make a typical user (1-10)?
5. What would you expect the app to do instead?
Think about:
- What happens if you click buttons really fast?
- What if your internet is slow/disconnected?
- What if you upload weird files/images?
- What if you try to break the app on purpose?
- What if multiple people use it at once?
- What if you use it on mobile/tablet?
- What if you refresh/navigate while it's working?
- What if you paste invalid inputs?
- What if you upload HUGE files?
- What if you leave it running overnight?
Don't worry about being technical - just describe what you saw break as a user.
Format each issue like:
ISSUE #1: [Brief angry user description]
- STEPS TO BREAK IT: [Exactly what you did]
- WHAT HAPPENED: [What you saw]
- ANGER LEVEL: [1-10]
- EXPECTED: [What should happen]
Keep going until you've found every possible way to break this app from a user's perspective!
After outpuiting the list, accoring to the list optmiced Composer edit block to fix the ones severe that make sense to adjust accoirng to gradio limitations and current usage target )dont suppose we need unecessary funcitons)
posted
an
update
16 days ago
Post
2288
Best Debug Prompt
You are a frustrated user who has tested this application extensively. Your job is to list EVERY possible way this app could completely break or become unusable.
For each potential failure:
1. What would make you say "This app is totally broken!"?
2. What exact steps did you take when it broke?
3. What did you see on your screen when it broke?
4. How angry would this make a typical user (1-10)?
5. What would you expect the app to do instead?
Think about:
- What happens if you click buttons really fast?
- What if your internet is slow/disconnected?
- What if you upload weird files/images?
- What if you try to break the app on purpose?
- What if multiple people use it at once?
- What if you use it on mobile/tablet?
- What if you refresh/navigate while it's working?
- What if you paste invalid inputs?
- What if you upload HUGE files?
- What if you leave it running overnight?
Don't worry about being technical - just describe what you saw break as a user.
Format each issue like:
ISSUE #1: [Brief angry user description]
- STEPS TO BREAK IT: [Exactly what you did]
- WHAT HAPPENED: [What you saw]
- ANGER LEVEL: [1-10]
- EXPECTED: [What should happen]
Keep going until you've found every possible way to break this app from a user's perspective!
After outpuiting the list, accoring to the list optmiced Composer edit block to fix the ones severe that make sense to adjust accoirng to gradio limitations and current usage target )dont suppose we need unecessary funcitons)
You are a frustrated user who has tested this application extensively. Your job is to list EVERY possible way this app could completely break or become unusable.
For each potential failure:
1. What would make you say "This app is totally broken!"?
2. What exact steps did you take when it broke?
3. What did you see on your screen when it broke?
4. How angry would this make a typical user (1-10)?
5. What would you expect the app to do instead?
Think about:
- What happens if you click buttons really fast?
- What if your internet is slow/disconnected?
- What if you upload weird files/images?
- What if you try to break the app on purpose?
- What if multiple people use it at once?
- What if you use it on mobile/tablet?
- What if you refresh/navigate while it's working?
- What if you paste invalid inputs?
- What if you upload HUGE files?
- What if you leave it running overnight?
Don't worry about being technical - just describe what you saw break as a user.
Format each issue like:
ISSUE #1: [Brief angry user description]
- STEPS TO BREAK IT: [Exactly what you did]
- WHAT HAPPENED: [What you saw]
- ANGER LEVEL: [1-10]
- EXPECTED: [What should happen]
Keep going until you've found every possible way to break this app from a user's perspective!
After outpuiting the list, accoring to the list optmiced Composer edit block to fix the ones severe that make sense to adjust accoirng to gradio limitations and current usage target )dont suppose we need unecessary funcitons)
Reacted to
automatedstockminingorg's
post with 👀
25 days ago
Post
1757
hi everyone, i have just uploaded my first fine tuned model, but serverless inference client is'nt available, its built with transformer architecture and is just a fine tuned llama 8b instruct. does anyone know how to make serverless inference available on a model?
- 6 replies