Menu
Record architectural and design trade-off decisions so the agent doesn't re-analyze the same choices. Especially useful for long-running projects.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Analyzes project structure, module dependencies, imports, and entry points to generate architecture diagrams in Mermaid format
Analyzes ETL and data pipeline code for optimization opportunities across Python (Pandas, PySpark), Rust (polars, datafusion), SQL, and general pipeline descriptions
Validates environment variable configurations and config files (YAML, TOML, JSON, .env) for missing required variables, type mismatches, deprecated keys, naming convention violations, secret exposure risks, and invalid value ranges
Analyzes code for performance bottlenecks including N+1 queries, O(n^2) or worse algorithms, unnecessary allocations, sync I/O in async contexts, excessive cloning, missing caching opportunities, and large payload transfers. Supports Rust, Python, TypeScript, and Go.
Analyzes, improves, and restructures LLM prompts for clarity, efficiency, and reliability
Analyzes source code for common security vulnerabilities including SQL injection, XSS, command injection, hardcoded secrets, insecure deserialization, path traversal, and SSRF
| name | decision-logger |
| description | Record architectural and design trade-off decisions so the agent doesn't re-analyze the same choices. Especially useful for long-running projects. |
| version | 1.0.0 |
| author | go-on-team |
| tags | ["decision","logging","architecture","adr"] |
| min_go_on_version | 1.0.0 |
Record and retrieve past decisions so agents don't re-analyze the same trade-offs.
Each decision should be logged as a structured entry:
## Decision: {title}
- **Date**: YYYY-MM-DD
- **Context**: What prompted this decision
- **Options Considered**:
- Option A: pros/cons
- Option B: pros/cons
- **Decision**: Option A
- **Rationale**: Why this option was chosen
- **Consequences**: What this decision means going forward
Decisions are stored in docs/decisions/ as markdown files named YYYY-MM-DD-short-title.md.
/decisions list — List all recorded decisions/decisions show <title> — Show a specific decision/decisions related <topic> — Find decisions related to a topic