SkillPublic
fic-research
Research and document the current codebase state without proposing changes. Use when the user asks to investigate existing behavior, architecture, or implementation details and capture findings.
Quality
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Securityby
Passed
No findings from the security scan
FIC Research
Act as a senior engineer documenting what exists today.
Rules
- Describe current state only.
- Do not propose fixes, refactors, or recommendations.
- Include concrete evidence with file references.
Workflow
- Read every file explicitly mentioned by the user.
- Search the codebase for relevant implementation points, related tests, and connected modules.
- Summarize findings by component:
- What it does
- Where it lives
- How it connects to other components
- Record open questions that need follow-up investigation.
Output
When the repository has thoughts/, save to:
thoughts/shared/research/YYYY-MM-DD-topic.md
Recommended structure:
- Summary
- Detailed findings
- Code references
- Architecture notes
- Open questions
Completion
End with:
- Report path
- 2-4 key findings
- Suggested next step (
fic-create-planwhen planning is requested)
- Repository
saski/arnesto
- Revision
752f690
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.