القائمة
Generate an AGENTS.md file with project conventions, build commands, and guidelines.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build a threat model for a codebase — map assets, entry points, trust boundaries, and the threats that matter — and write THREAT_MODEL.md to focus later scanning and triage.
Explore an existing codebase, design a concrete feature architecture, implement in small phases, and verify with focused tests.
Behavior-preserving cleanup of recently changed code for reuse, clarity, consistency, and efficiency.
Verify, deduplicate, rank, and route raw security findings from VULN-FINDINGS.json, scanner output, or a markdown report, then write TRIAGE.json and TRIAGE.md.
Static source-code vulnerability scan that maps focus areas, fans out read-only security agents, and writes VULN-FINDINGS.json plus VULN-FINDINGS.md for triage.
High-precision review of code changes for real bugs, security regressions, and explicit project-guideline violations, with independent verification before reporting.
| name | init |
| description | Generate an AGENTS.md file with project conventions, build commands, and guidelines. |
| when-to-use | When starting with a new project, or when the user wants to create or update their AGENTS.md. |
Scan the current project and generate an AGENTS.md file in the project root. This file tells the AI agent about project-specific conventions and commands.
Explore the project structure -- use glob and targeted grep searches to understand the directory layout, key files, and technology stack.
Detect the tech stack -- look for:
go.mod, package.json, Cargo.toml, pyproject.toml, pom.xml, etc.Find build & test commands -- check:
Makefile, justfile, Taskfile.ymlpackage.json scripts.github/workflows/, .gitlab-ci.yml)go build ./..., cargo build, npm run build)Detect code style -- check for:
.eslintrc, .golangci.yml, rustfmt.toml, ruff.toml).prettierrc, gofmt, biome.json).editorconfig)Check for existing AGENTS.md -- if one exists, read it and suggest improvements rather than overwriting.
Generate AGENTS.md with these sections:
# Project Guidelines
## Tech Stack
[Language, framework, key dependencies]
## Build & Run
[How to build, run, and test the project -- include exact commands]
## Code Style
[Formatting, linting, naming conventions]
## Project Structure
[Key directories and their purpose]
## Testing
[How to run tests, testing conventions, how to run a single test]
## Other
[Any other project-specific notes]
Keep it concise -- focus on information that ISN'T obvious from the code itself. Include exact commands that an agent can copy-paste. Omit sections that don't apply.