Sharper Flow
Official@sharper-flow
Offers architectural governance, codebase drift detection, and engineering quality assurance through structured repository analysis and module dependency management.
Agent Skills by Sharper Flow
Showing 25 vetted skills indexed across 1 GitHub repositories.
Sharper-Flowadv-zoom-out
Map code segments to modules and caller relationships for architectural overviews.
Sharper-Flowadv-instructions-audit
Audit documentation claims against executable test anchors for system fidelity.
Sharper-Flowadv-user-intuit
Present candidate comparisons and capture user preferences via a question tool.
Sharper-Flowadv-cleanup
Automate triage of stale, duplicate, or abandoned engineering changes in Advance-governed repositories.
Sharper-Flowadv-audit
Detect engineering drift by comparing codebases against specifications and enforcing quality gates.
Sharper-Flowadv-skill-author
Standardize agent skill creation with YAML frontmatter and progressive disclosure.
Sharper-Flowadv-ci-release
Automate release lifecycle with semver versioning and GitHub releases.
Sharper-Flowadv-refactor
Detect drift between stale engineering proposals and current codebases.
Sharper-Flowadv-improve
Analyze repository state to identify evidence-backed improvement opportunities across security, reliability, and architecture.
Sharper-Flowadv-backend-stack-eval
Evaluate backend technology stacks using architectural decision frameworks.
Sharper-Flowadv-frontend-review
Audit frontend components across six engineering and design dimensions.
Sharper-Flowadv-opportunity-scout
Identify missed opportunities and design leverage points in AI-assisted engineering workflows.
Sharper-Flowadv-codebase-design
Standardize software module architecture with deep-module principles and seam-based dependency management.
Sharper-Flowadv-slop-detection
Detect and categorize AI-generated code quality issues via AST analysis and regex patterns.
Sharper-Flowadv-worktree
Manage git worktree lifecycles with Temporal state orchestration and merge-before-delete safety.
Sharper-Flowadv-prototype
Create throwaway prototypes to validate business logic and UI designs.
Sharper-Flowadv-comp-research
Analyze GitHub repositories and web content to extract competitive feature and pricing details.
Sharper-Flowadv-tron
Map codebase structure and identify high-risk hotspots with read-only analysis.
Sharper-Flowadv-arch-detection
Detect architectural inconsistencies and dependency violations across technology stacks.
Sharper-Flowadv-agent-tool-contracts
Enforce Zod schema validation and context packet alignment for agent-callable tools.
Sharper-Flowadv-improve-codebase-architecture
Identify shallow modules and generate HTML reports with Mermaid diagrams.
Sharper-Flowadv-diagnose
Execute a multi-phase diagnostic workflow to isolate and resolve software bugs.
Sharper-Flowadv-clarify
Generate Socratic questions to resolve ambiguity in engineering specifications.
Sharper-Flowadv-triage
Reconcile GitHub issues, ADV changes, and local artifacts into a governed backlog.
Frequently Asked Questions About Sharper Flow
FAQPage SchemaWhat specific engineering tasks does Sharper Flow enable?▼
Sharper Flow enables architectural drift detection, codebase structure mapping, Zod schema validation for interface contracts, and automated triage of stale engineering changes. It provides deep-module analysis, Mermaid diagram generation for architecture visualization, and structured postmortem reporting based on historical change data.
Which personas benefit most from these capabilities?▼
Software architects, engineering managers, and senior developers benefit from these capabilities. The system is designed for technical leads responsible for maintaining codebase integrity, enforcing quality gates, and ensuring architectural consistency across large-scale repositories and distributed engineering teams.
What are the prerequisites for implementing these analysis capabilities?▼
Implementation requires a GitHub-hosted repository and adherence to the Advance-governed structure. Users must define specifications for comparison, as the system relies on these anchors to detect drift, validate module dependencies, and enforce quality gates against the current codebase state.