agent-skills
llms.txt4 starsChanged 3 months agoMITView on GitHub
Agent Instructions This file outlines the required constraints and methodologies for AI coding assistants operating on projects utilizing the agent-skills repository. 1. Structural Refactoring [Trigger]: ANY time you need to search for code structure, refactor symbols, analyze impact, find dead code, or trace dependencies. [Skill Requirement]: You must use the ast-code-graph skill. Do not rely on LLM context windows or regex text search for structural modifications. Use the ast-grep tool to parse the AST semantically and generate JSON outputs. 2.…
Files
> Agent Instructions > This file outlines the required constraints and methodologies for AI coding assistants operating on projects utilizing the `agent-skills` repository. 1. Structural Refactoring [Trigger]: ANY time you need to search for code structure, refactor symbols, analyze impact, find dead code, or trace dependencies. [Skill Requirement]: You must use the `ast-code-graph` skill. Do not rely on LLM context windows or regex text search for structural modifications. Use the `ast-grep` tool to parse the AST semantically and generate JSON outputs. 2. Bug Fixing & Diagnostics [Trigger]: AUTOMATICALLY anytime you encounter a stack trace, test failure, production bug, or unexpected behavior. [Skill Requirement]: You must use the `systematic-debugging` skill. No fixes without a root cause investigation first. Do not guess. Do not supply quick patches. You must reproduce the bug using a script, heavily utilize `grep_search` to understand context, and trace boundaries. Escalation is MANDATORY after 3 failed fix attempts. 3. Structural Code Refactoring [Trigger]: ANY time you need to do bulk structural replacements across files — renaming function arguments at call sites, migrating deprecated API call shapes, rewriting patterns that regex/sed would botch (nested parens, multiline, string boundary issues), extracting code locations with file+line output. Also trigger for Python 2 → 3 migrations. [Skill Requirement]: You must use the `structural-refactor` skill. Do NOT use `sed` or raw regex for structural code changes. Use `comby` for cross-language pattern replacement, `2to3` for Python 2 → 3 migrations, and `pyupgrade` to modernize Python 3 idioms. Always run a preview step (`-diff` or dry-run) before applying changes in-place. 4. Continuous Improvement [Trigger]: ALWAYS at the end of complex tasks, debugging sessions, or when learning a new project codebase quirk. [Skill Requirement]: You must use the `self-reflection` skill before closing a complex task. Codify the hard-won project lessons into markdown format so future AI agents do not repeat the same mistakes.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ast-code-graphSkill
- ast-grepSkill
- self-reflectionSkill
- structural-refactorSkill
- systematic-debuggingSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.