/templates/gov-code-search-template.md

Government Code Search Report: [PROJECT_NAME]

Template Origin: Official | ArcKit Version: [VERSION] | Command: /arckit:gov-code-search

Document Control

Revision History

Version	Date	Author	Changes	Approved By	Approval Date
[VERSION]	[DATE]	ArcKit AI	Initial creation from /arckit:gov-code-search agent	PENDING	PENDING

---

Executive Summary

Search Query

Original Query: [original search query entered by user]

Query Variations Used:

• [variation 1]
• [variation 2]
• [variation 3]

Platforms Searched: [GitHub (GOV.UK organisations), GitLab, code.gov, Data.gov.uk repositories, etc.]

Results Found

Total Repositories Scanned: [X]

High Relevance Results: [X]

Medium Relevance Results: [X]

Low Relevance / Excluded: [X]

Top Results

#	Repository	Organisation	Relevance	Language	Last Active
1	[repo-name]	[Organisation]	High	[Language]	[YYYY-MM-DD]
2	[repo-name]	[Organisation]	High	[Language]	[YYYY-MM-DD]
3	[repo-name]	[Organisation]	High	[Language]	[YYYY-MM-DD]
4	[repo-name]	[Organisation]	Medium	[Language]	[YYYY-MM-DD]
5	[repo-name]	[Organisation]	Medium	[Language]	[YYYY-MM-DD]

---

Search Results

High Relevance Results

[REPOSITORY_NAME_1]

Attribute	Value
Organisation	[Government Organisation]
Repository URL	[https://github.com/organisation/repo]
Description	[Repository description]
Language	[Primary language(s)]
License	[MIT / Apache 2.0 / OGL v3.0 / Crown Copyright]
Last Activity	[YYYY-MM-DD]
Stars	[X]

Why Relevant: [Explain why this repository matches the search query and project needs]

Key Patterns:

• [Pattern 1: e.g., Uses GOV.UK Design System components]
• [Pattern 2: e.g., Implements OWASP Top 10 security controls]
• [Pattern 3: e.g., Follows GDS Service Manual API design principles]

---

[REPOSITORY_NAME_2]

Attribute	Value
Organisation	[Government Organisation]
Repository URL	[https://github.com/organisation/repo]
Description	[Repository description]
Language	[Primary language(s)]
License	[MIT / Apache 2.0 / OGL v3.0 / Crown Copyright]
Last Activity	[YYYY-MM-DD]
Stars	[X]

Why Relevant: [Explain relevance]

Key Patterns:

• [Pattern 1]
• [Pattern 2]

---

[REPOSITORY_NAME_3]

[Repeat repository card structure for additional high relevance results]

---

Medium Relevance Results

[REPOSITORY_NAME_4]

Attribute	Value
Organisation	[Government Organisation]
Repository URL	[https://github.com/organisation/repo]
Description	[Repository description]
Language	[Primary language(s)]
License	[MIT / Apache 2.0 / OGL v3.0 / Crown Copyright]
Last Activity	[YYYY-MM-DD]
Stars	[X]

Why Relevant: [Explain partial relevance and what aspects match]

Key Patterns:

• [Pattern 1]
• [Pattern 2]

---

[REPOSITORY_NAME_5]

[Repeat repository card structure for additional medium relevance results]

---

Code Patterns Identified

Pattern	Repositories Using It	Description
[Pattern Name 1]	[Repo A, Repo B, Repo C]	[What this pattern does and why it is common across government]
[Pattern Name 2]	[Repo A, Repo D]	[Description]
[Pattern Name 3]	[Repo B, Repo E]	[Description]
[Pattern Name 4]	[Repo C]	[Description]

Observations: [Narrative on common patterns found — e.g., GOV.UK Frontend adoption, use of 12-factor app methodology, cloud-native patterns on GCP/AWS, common authentication approaches]

---

Implementation Approaches Compared

Approach	Used By	Pros	Cons
[Approach 1, e.g., Monolithic Rails app]	[Repo A, Repo B]	Simple to deploy, well understood	Scaling limitations, harder to test in isolation
[Approach 2, e.g., Microservices + API gateway]	[Repo C, Repo D]	Independent scaling, clear boundaries	Operational complexity, distributed tracing needed
[Approach 3, e.g., Serverless functions]	[Repo E]	Low cost at low volume, no infra management	Cold starts, vendor lock-in, harder to test locally

Recommended Approach for This Project: [Name] — [Brief rationale based on project requirements and team capabilities]

---

Recommendations

Immediate Next Steps

1. Clone and Review: [Repo Name] — [Specific aspects to examine]
2. License Verification: Confirm [Repo Name] license permits [intended use]
3. Tech Stack Spike: Prototype integration of [Repo Name] with project stack
4. Community Contact: Reach out to [Organisation] team regarding [Repo Name] reuse intentions

Search Refinements

If further searching is needed, consider these refined queries:

• [Refined query 1] — [What this would surface]
• [Refined query 2] — [What this would surface]

Related ArcKit Commands

• Run /arckit:gov-reuse for a full reusability assessment of shortlisted repositories
• Run /arckit:gov-landscape for a broader landscape analysis of [domain] across government

---

External References

This section provides traceability from generated content back to source documents. Follow citation instructions in the project's citation reference guide.

Document Register

Doc ID	Filename	Type	Source Location	Description
None provided	—	—	—	—

Citations

Citation ID	Doc ID	Page/Section	Category	Quoted Passage
—	—	—	—	—

Unreferenced Documents

Filename	Source Location	Reason
—	—	—

---

Generated by: ArcKit /arckit:gov-code-search agent Generated on: [DATE] ArcKit Version: [VERSION] Project: [PROJECT_NAME] Model: [AI_MODEL]