Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill github-issue-structure-for-personal-finance-tracking --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Github Issue Structure For Personal Finance Tracking?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-github-issue-structure-for-personal-finance-tracki-workspace-hub)More formats (shields.io, HTML) on the badges page.
---
name: github-issue-structure-for-personal-finance-tracking
description: Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)
version: 1.0.0
source: auto-extracted
extracted: 2026-04-13
metadata:
tags: ["github-workflow", "financial-tracking", "repo-organization", "issue-design"]
---
# GitHub Issue Structure for Personal Finance Tracking
When building financial analysis systems, separate **confidential data/config** (private personal repo) from **algorithms/logic** (shared/public repo). Create the tracking issue in the data repo with clear references to algorithm repos where implementation lives. This enables sensitive portfolio info to stay private while keeping reusable code modular and potentially shareable. Flag browser access limitations early (e.g., Fidelity blocked by safety extensions) and establish manual data handoff workflows.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
